Execution History
Every workflow run is logged with detailed information about what happened, when it happened, and whether it succeeded. Use the execution history to monitor your workflows, verify they're running as expected, and troubleshoot any issues.
Viewing Execution History
Finding History for a Workflow
The history list shows runs in reverse chronological order, with the most recent at the top.
Information Displayed
Each entry in the execution history shows:
| Field | Description |
| Scheduled Time | When the run was supposed to start (for scheduled workflows) |
| Actual Time | When the run actually began executing |
| Status | Current state of the run (see status definitions below) |
| Duration | How long the run took to complete |
| Trigger | What initiated the run (schedule, manual, webhook, etc.) |
Understanding Run Status
Each workflow run has one of the following statuses:
Completed
The workflow ran successfully from start to finish. All steps executed without errors, and any expected outputs were produced.
Failed
An error occurred during execution. The workflow stopped before completing all steps. See the Troubleshooting Failed Runs section for how to diagnose and fix failures.
Cancelled
The run was stopped before completion. This happens when:
Running
The workflow is currently executing. Refresh the page or wait for the run to complete to see final results.
Pending Approval
The workflow has reached a step that requires user approval before continuing. The run is paused until someone approves or denies the pending action. Check your notifications or the approval queue to take action.
Viewing Run Details
Click on any run in the history list to see complete details about what happened.
Run Overview
The detail view shows:
Conversation Thread
Each workflow run creates a conversation thread that captures the entire execution flow. To view it:
The conversation thread includes:
Tool Calls
The run details show which tools were invoked during execution:
This information helps you understand exactly what actions the workflow performed.
Troubleshooting Failed Runs
Finding Error Messages
When a run fails:
The conversation thread also shows where the failure occurred. Scroll through to find the step that failed and see the context around the error.
Common Failure Reasons
Authentication ErrorsThe connector lost access to the external service. Re-authenticate the connector in your integrations settings.
Rate LimitingThe external service rejected requests due to too many calls. The workflow may succeed if you run it again later, or consider reducing the frequency of scheduled runs.
Invalid DataThe workflow received unexpected data that it couldn't process. Check the input data and any upstream systems that provide data to the workflow.
TimeoutThe workflow took too long to complete. This can happen with complex workflows or slow external services. Consider breaking the workflow into smaller pieces.
Tool Not FoundA tool referenced in the workflow is no longer available. The connector may have been disconnected or the tool removed.
Approval TimeoutA step requiring approval was not acted on within the allowed time window.
What to Do Next
If the issue persists after investigation, you may need to edit the workflow to handle the error case or adjust your integrations.
Zenmako