Run History
Monitor your workflow runs and debug issues when things don't work as expected.
Viewing Run History
How to access run history
- 1Open your workflow from the Workflows list
- 2Click the "Runs" button in the toolbar (shows run count)
- 3The run history panel opens on the right side
- 4Browse runs by date with their status (completed, failed, running)
- 5Click on any run to see detailed logs for each node
Run Statuses
Each workflow run has a status indicating whether it completed successfully.
Completed
All nodes in the workflow executed successfully. Data was sent to all configured destinations.
Failed
One or more nodes encountered an error. Click on the run to see which node failed and the error message.
Running
The workflow is currently executing. This is usually brief unless there are delays or long-running AI operations.
Queued
The run is waiting to be processed. This happens when the workflow is paused or when there are delay nodes.
Run Details
Click on any run to see detailed information about what happened.
What you'll see
- Trigger data — The form submission that started the workflow, including all field values
- Node execution order — Which nodes ran and in what order
- Node outputs — The data produced by each node (enrichment results, AI outputs, etc.)
- Error messages — If a node failed, the specific error message and stack trace
- Timing — When each node started and how long it took to execute
Troubleshooting Common Issues
Workflow not triggering
- • Make sure the workflow is Active, not Draft or Paused
- • Verify the correct form is selected in the trigger node
- • Check that you're submitting the connected form, not a different one
- • Form must be published for submissions to trigger workflows
Data not appearing in destination
- • Check run history for errors on the destination node
- • Verify the integration is still connected (token may have expired)
- • Check field mappings are configured correctly
- • Look for filter nodes that might be blocking the submission
- • Verify API rate limits haven't been exceeded on the destination
Workflow paused unexpectedly
- • An integration may have disconnected — re-authenticate it
- • Repeated errors can cause auto-pause to prevent data loss
- • Check the pause reason shown in the workflow toolbar
- • Fix the issue, then resume and choose whether to process queued runs
AI agent errors
- • Check if you have remaining AI credits (Business plan required)
- • Review the prompt for any issues or missing variables
- • Very long form responses may hit token limits — use summarization
- • Check the error message for specific details
Handling Paused Workflows
When a workflow is paused, new submissions are queued instead of being processed immediately.
Resuming a paused workflow
- 1Open the paused workflow to see the pause reason
- 2Fix the underlying issue (reconnect integration, fix configuration, etc.)
- 3Click "Resume" in the toolbar
- 4Choose what to do with queued submissions:
Process all: Run the workflow for all queued submissions
Skip queue: Discard queued submissions and start fresh
Don't process: Keep queued submissions but don't run them automatically
Did this answer your question?