Execution logs
Learn how to view, understand, and debug workflow executions using logs in NocoDB.
Execution Logs provide complete visibility into how a workflow runs in NocoDB. Every time a workflow is triggered, NocoDB records detailed execution data—making it easy to monitor progress, verify outcomes, and troubleshoot failures.
Execution logs help you understand what triggered the workflow, how each node executed, and where issues occurred, all in a single, structured view. This is especially useful when building complex workflows with multiple actions, integrations, or conditional logic.
Accessing execution logs
To view workflow execution logs:
- Open the workflow
- In the top toolbar, click the Logs tab
- Select an execution run to inspect its details
Each run represents a single execution of the workflow, captured from trigger to completion.
Log views
Execution list
View all workflow runs along with their execution status and timestamps. This view helps you quickly identify successful runs, failures, and recent activity.
Execution summary
Get a high-level overview of the selected execution, including trigger information and overall workflow status. This summary provides quick context before diving into individual node details.
Node execution details
Inspect execution details for each node in the workflow. Selecting a node displays its inputs, outputs, and execution status, making it easy to trace data flow and pinpoint errors.
Pending executions
When you publish changes to a workflow, some executions may already be paused and waiting to resume (for example, at a Delay or Wait Until node). Log entries for these pending executions indicate their paused status.
In such cases, NocoDB prompts you to decide how those pending executions should be handled.
Available options
-
Let them continue with old version Pending executions resume using the previously published version of the workflow. Any new changes you are publishing apply only to future executions.
-
Cancel pending executions All paused executions waiting to resume are stopped permanently and will not continue. Only newly triggered executions will use the updated workflow version.
Iterator logs
When a workflow processes multiple records using an Iterate node, NocoDB logs each iteration separately. Iterator logs help you understand how the workflow behaves for every item in a collection and debug issues at a specific iteration.
Iteration navigation
For executions involving an Iterate node, the log view displays an iteration selector:
- Indicates the current iteration number and the total number of items (for example,
3 / 16) - Lets you move between iterations using the previous and next controls
- Updates node inputs, outputs, and logs based on the selected iteration
This makes it easy to inspect how data changes across iterations.
Iteration-specific execution details
When an iteration is selected:
- Node execution status reflects only that iteration
- Inputs show the record or item being processed in the current loop
- Outputs display results generated for that specific item
- Logs capture messages related to the selected iteration only
This is especially useful when:
- A workflow succeeds for some items but fails for others
- You need to verify record-level transformations
- Debugging conditional logic inside loops