Execution History
Every execution is recorded in the execution history. You can browse all past runs, re-inspect their results, replay them with the same trigger data, or compare runs to identify regressions.
Accessing Execution History
In Execution Mode, click the History icon in the Top Toolbar (clock icon). This opens the Execution History panel — a list of all past runs for this ProcessThread.
History List Columns
| Column | Description |
|---|---|
| Execution ID | Unique GUID. Click to copy. |
| Status | Completed / Failed / Cancelled / Paused |
| Started At | When the execution began |
| Duration | Total elapsed time in human-friendly format |
| Triggered By | User name or system (webhook, schedule) |
| Node Count | Total nodes / completed nodes / failed nodes |
Replaying a Past Execution
Select any past execution in the history list and click Re-run. This opens the Run dialog pre-populated with the original trigger data from that execution. You can modify the trigger data before confirming, or re-run with exactly the same input to reproduce an issue.
Inspecting a Past Execution
Click any past execution row to load its results into the Observer Panel. The canvas shows the node statuses from that historical run (blue outline indicates this is historical, not live). All four Observer Panel tabs (Status, Node List, Logs, Inspector) work against the historical execution data.
History Retention
Execution history is retained according to your tenant's data retention policy (default: 90 days). Log data within each execution has its own retention policy (default: 30 days). After log retention expires, the execution record remains but log details are removed.