Execution History
View and filter past workflow runs.
The Executions page lets you inspect past runs for each workflow. Navigate to Executions in the sidebar.
Layout
- Workflow selector - pick a workflow from the sidebar on desktop or top pills on mobile
- Status filter - filter runs by: all, pending, success, or failed
- Run list - paginated list of executions for the selected workflow
- Detail panel - opens when you select a run, showing node-level results without leaving the page
Columns
Each execution row shows:
| Column | Description |
|---|---|
| Status | pending, running, waiting, success, or failed |
| Nodes | Count of nodes executed, including success/failure summary |
| Started | When the execution began |
| Duration | How long the run took |
The workflow editor's executions panel adds extra context on top of the history list, including automatic run labels, user notes, source badges, and AI cost/token chips when available.
Clicking a run
Click any execution row to open details. The panel shows node-level output, errors, timing, and copy/debug information without leaving the page.
From the workflow editor, the executions panel also includes recent-run notes, a node mini-map, node-run search, and failed-node filtering for faster debugging.
Deleting execution logs
Use the delete button on a finished execution to remove that execution log. Running, waiting, or pending executions cannot be deleted from the list. Deleting a log does not delete the workflow.
Retention window
Execution logs are retained for approximately 7 days from when the run started - not from when it finished. A daily cleanup sweep removes terminal runs whose start time is older than that, along with their node-run details and any per-iteration ForEach data. Because the sweep runs on a 24-hour cycle, individual rows may persist up to roughly 8 days before being collected - but past the 7-day mark, expect the run to disappear at any time. The workflow itself is unaffected; only the historical run record is removed.
For a long-running workflow that takes hours or days (paused ForEach loops, scheduled retries), the retention window starts from the original start, not from completion. A run that started 6 days ago and finished today will be eligible for cleanup tomorrow.
Run-level loop credit and payment records are preserved indefinitely as part of the financial audit trail; only the operational history (node outputs, errors, ForEach iteration data) is subject to retention.
If you need a permanent record of a specific run, copy any details you need from the run-detail panel before the retention window expires.
Preview runs
Code and Transform preview runs are hidden from the main execution list. They still appear in lifetime usage counts so you can distinguish normal workflow runs from preview activity.
Pagination
Results are paginated. Scroll down or click Load more to see older runs.
Next steps
- Run Detail - node-level run inspection
- Error Handling - diagnosing failures
- Running a Workflow - editor-side run panel