# Execution History (/docs/executions/history)

View and filter past workflow runs.



The Executions page is the run log for your whole account. Navigate to **Executions** in the sidebar.

By default it shows **every run across every workflow**, newest first, so you can see what fired overnight without picking a workflow first. Narrow it when you want to.

Filters [#filters]

* **Workflow** - a searchable picker. Leave it on *All workflows* for the account-wide view, or type to find one workflow and scope the list to it.
* **Status** - all, running, pending, success, failed, or canceled.

Both filters are applied by the server, so they search your entire run history rather than only the rows currently on screen. When a filter is active a **Clear** button appears next to it.

Columns [#columns]

Each row is one run:

| Column   | Description                                                                                                                                                              |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Run      | The run's status: running, pending, waiting, success, failed, or canceled. In-flight runs show a spinner.                                                                |
| Workflow | Which workflow ran, plus its automatic run label when one was derived (for example the trade it made).                                                                   |
| Trigger  | What started it: Manual, Cron, or Webhook.                                                                                                                               |
| Outcome  | The most useful column. A failed run names **the node it died on** ("failed at Jupiter swap"). A finished run reports its node tally. An in-flight run reports progress. |
| Cost     | Model spend for the run, with token count on hover. Runs that used no AI show nothing here rather than a misleading $0.                                                  |
| Took     | How long the run took. Ticks live while the run is in flight.                                                                                                            |
| Started  | When the run began.                                                                                                                                                      |

Narrow screens drop columns from the right, keeping status and workflow name longest.

Opening a run [#opening-a-run]

Click any row and it expands **in place** into a node-by-node waterfall. Each node gets a bar positioned at its real offset and width inside the run, so a slow node looks slow instead of being a number you have to read. See [Run Detail](/docs/executions/run-detail) for what's inside.

The list stays where it is, so you can open several runs and compare them. Click the row again to collapse it.

From the workflow editor, the executions panel adds editor-only context on top of this: user notes, a node mini-map, node-run search, and failed-node filtering.

Deleting execution logs [#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 [#retention-window]

Execution logs are retained for **approximately 7 days from when the run started** - not from when it finished. A cleanup sweep removes terminal runs whose start time is older than that, along with their node-run details and any per-iteration ForEach data. The sweep runs hourly, so 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.

**High-frequency schedules keep less.** Workflows running on a schedule faster than every 5 minutes (for example every minute, or every 2 minutes) keep only **roughly the last 30 hours** of run history instead of 7 days. These workflows can fire \~1,440 times a day, so their run history is treated as ephemeral and aged out sooner. Everything else about retention (financial records preserved, workflow unaffected) is the same.

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 credit ledger 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, expand it and copy any details you need before the retention window expires.

Preview runs [#preview-runs]

Code and Transform preview runs are hidden from the main execution list. They still appear in lifetime usage analytics so you can distinguish normal workflow runs from preview activity.

Pagination [#pagination]

Results are paginated. Scroll down or click **Load more** to see older runs.

Next steps [#next-steps]

* [Run Detail](/docs/executions/run-detail) - node-level run inspection
* [Error Handling](/docs/executions/errors) - diagnosing failures
* [Running a Workflow](/docs/editor/running) - editor-side run panel