Debugging
Inspect flow executions to find and fix issues.
Execution History
Click the History tab in the flow editor to see all past executions.
Each entry shows:
- Status: finished (green), error (red), stopped (yellow)
- Duration: total execution time
- Timestamp: when it ran
Per-Block Results
Click an execution to expand it. Each block shows:
- Status: OK, ERROR, or STOP
- Duration: how long that block took
- Outputs: all values produced by the block
This lets you trace exactly where data flows and where errors occur.
Test Mode
Click the play button in the flow editor to run a test execution with sample data. The results appear immediately in the history panel.
Common Issues
| Problem | Solution |
|---|---|
| Block shows ERROR | Check the error message — usually a missing input or invalid data |
| Output is empty | Verify the input is connected (drag from previous block's output) |
| Flow doesn't trigger | Check that the flow is enabled and the connection is active |
Vault value shows {{vault.KEY}} | Re-save the flow so values are re-resolved, and verify the secret exists in the vault |
| HTTP request fails | Check URL, headers, and that the target isn't a private address |
Helper Flow History
When ForEach calls a helper flow, each iteration creates a separate history entry in the helper flow. This lets you inspect what data was passed in each iteration.