History range
The execution history view has a range selector to control how far back you can see runs.| Range | Availability |
|---|---|
| Last 24 hours | All plans |
| Last 7 days | All plans |
| Last 30 days | Enterprise plan only |
Execution statuses
| Status | Description |
|---|---|
| Pending | Queued, waiting to start |
| Running | Currently executing steps |
| Waiting | Paused on a delay node |
| Completed | Finished successfully |
| Failed | An error occurred |
| Cancelled | Manually stopped |
What’s tracked
Each execution records:- Trigger type and data — What started the workflow and the data it carried
- Current position — Which node is executing (or waiting)
- Step outputs — The result of each completed step
- Error details — What went wrong if a step failed
- Timestamps — When it started, completed, or failed
Step outputs
Every action stores its output after running. These outputs are available to later steps as variables. For example, a voice call step stores:- Call ID
- Status and call disposition
- Success evaluation result
- Extracted data fields
- Recording URL
- HTTP status code
- Response body
Testing
Individual steps can be tested from within their configuration panel. Step-level testing lets you verify each action works correctly before publishing. Test executions are flagged separately and don’t count against limits.Troubleshooting
Workflow didn’t trigger
- Check that the workflow is published and the activate/deactivate toggle is set to active
- Verify the trigger conditions match the event
- Check deduplication — the same trigger for the same contact within the dedup window (default 1 minute) is ignored
Step failed
- Check the error message in the execution details
- Common causes: missing integration connection, invalid phone/email, expired OAuth token
- Transient failures (network issues, rate limits) are retried automatically up to 3 times