Understanding Execution Logs

Learn how to read and use execution logs to monitor and debug your workflows.

Overview

Every workflow run is recorded as an Execution. The Executions page is the central source of truth for what happened: which workflow ran, what triggered it, when, how long it took, and the input/output of every step. When something goes wrong, this is where you go.

Each execution captures both the high-level status (success, failed, running, pending) and step-by-step details for each node. You can drill from the list view into a single execution, and from there into a single step's payload, error, and timing.

Accessing Execution Logs

Open Executions from the left sidebar. Each row shows:

• Workflow name - the workflow that ran.
• Status - success, failed, running, or pending.
• Trigger type - manual, schedule, webhook, or email.
• Start time - when the trigger fired.
• Duration - end-to-end time from trigger to last step.

Filters

• Status - narrow to failed, successful, or running runs.
• Workflow - filter to a single workflow.
• Trigger Type - filter by how the workflow was started.
• Date Range - constrain to a window.

Inside an Execution

• Step results - each node's input data, output data, and status.
• Error messages - failed steps show the error and stack trace; the offending step is highlighted in red.
• Timing - per-step duration plus a timeline view of the full run.
• Variables - the variables in scope at each step, useful for debugging template expressions.

Debugging Failures

1. Filter the Executions list to Failed and find the run.
2. Open it and locate the red step.
3. Read the error message - it usually identifies the API or template that failed.
4. Inspect the input payload to the failed step. Most failures are unexpected data shape or missing fields.
5. Open the workflow in the designer, fix the issue, save, and run again.

Tips

• Copy the execution URL into support requests - it's the fastest way for support to find the run.
• For repeated failures, check the connection on the Connections page. Expired tokens cause cascading failures.
• Use the date range filter when investigating issues from a specific deploy or change.

Common Pitfalls

• Looking in the wrong workspace. Switch workspaces if the run isn't where you expect.
• Reading only the latest failure - check whether the same step has been failing on every run for a clearer pattern.
• Mistaking pending for stuck. Workflows with Human Approval or long-running steps sit in pending intentionally.

Related Articles

• Monitoring Workflow Executions
• Understanding Retry and Error Handling
• Running Your First Workflow
• Troubleshooting Connection Issues
• Dashboard Overview

Learn More

• Execution monitoring documentation