Execution history (per workflow)
Every workflow has its own history page at /workflow/<id>/history. It's a table of every run of this workflow.
For a global view across all workflows, use the log explorer. For a single execution's full detail, click any row to drill into the execution detail page.
📸 Screenshot needed:
execution__history-table.png, Execution history table for a workflow showing 8 rows with mixed success / failed statuses, columns for Execution ID, Status, Started, Duration, Trigger, Last node state.
How to get there
Two paths:
- From the workflow editor, click the History breadcrumb (or
⌘⇧L). - From the workflow list (
/workflows), click the card's overflow menu → View history.
What's on the screen
A toolbar plus a table.
Toolbar
- Date range, last 24 h, 7 days, 30 days, or custom.
- Status filter, chips for
success,failed,cancelled,timeout,waitingForInput,running. - Trigger filter, narrow by which trigger fired (manual, webhook, schedule, …).
- Search, by execution ID.
- Refresh, fetch latest. Optional Live refresh toggle (3-second polling).
- Export, CSV of the visible rows.
Columns
| Column | Notes |
|---|---|
| Execution ID | Truncated UUID; click to copy full ID, or click the row to open details |
| Status | Coloured badge, green / red / grey / yellow / blue |
| Started | Local-time timestamp; hover for full ISO 8601 |
| Duration | Elapsed time from pending → terminal state |
| Trigger | Manual / Webhook / Schedule / API / Connector event |
| Last node | Name of the last node that ran; helpful for spotting where failures happened |
| Input summary | Short preview of trigger payload (expand for full) |
Sort by any column by clicking its header.
Row actions
Right-click any row:
- Open detail
- Open as workflow snapshot, load this run's state into the editor canvas read-only
- Copy execution ID
- Replay, run the workflow again with this run's input
- Cancel, only for non-terminal runs
Replaying a run
Two flavours:
- Replay (same input), runs the current workflow version against the input that was used last time. Good for verifying a fix.
- Replay (this version), pins the workflow version from the original run plus the same input. Closer to "rerun exactly what ran".
Replays show up as fresh executions in history with a back-reference to the original.
Empty state
A new workflow with no runs shows: "No executions yet. Click Run in the editor or trigger this workflow to see runs here."
Tips & gotchas
- Pagination cap. The history page shows up to 1 000 rows. Older runs are still available, use the log explorer for unbounded search.
- Live refresh costs API. Leave it off for production unless you're actively debugging.
- Failed runs sometimes have a successful "last node", that's the last node that ran, which can be on a recovery path after an error-handling branch. Don't read "last node = success" as "workflow succeeded".
- Trigger filter is exact, not regex. To find all runs triggered by any webhook, pick
Webhookfrom the chip filter.
Related
- Log explorer, cross-workflow search
- Execution detail, per-run drill-down
- Replaying
Found something out of date? This page lives in the Flero docs content set.