Every workflow execution is automatically logged in the history. This provides a complete record of when workflows ran, how long they took, and whether they succeeded or failed.
Accessing History
Click the History tab at the top of the workflow editor to view execution history. This tab appears next to the Blocks tab and displays all past runs in chronological order.
The most recent executions appear at the top of the list.
Understanding History Entries
Each history entry displays key information about the execution:
| Field | Description |
|---|---|
| Timestamp | Relative time since execution (e.g., "58 seconds ago") |
| Ran by | User who triggered the execution |
| Started at | Exact date and time the workflow began |
| Duration | Total execution time |
| Triggered by | How the workflow was started (Manual run, Schedule, etc.) |
Failed executions display an error message indicating which node failed and at what step.
Filtering by State
Use the state filter dropdown to show only executions with specific outcomes:
| State | Description |
|---|---|
| All states | Shows every execution regardless of outcome |
| Success | Shows only successful completions |
| Failed | Shows only failed executions with errors |
| Running | Shows currently executing workflows |
| Cancelled | Shows executions that were manually stopped |
Click the dropdown at the top of the history panel to select a filter. The list updates immediately to show matching entries.
Viewing Execution Details
Click any history entry to view detailed results from that run. This opens the same result view you see after manually running a workflow.
The detail view shows output data from each block. You can examine results in table or map format just like current executions.
Block-level errors appear highlighted in the detail view. This makes it easy to identify which block caused a failure and why.
Debugging with History
Compare successful and failed runs to identify what changed. Look at execution duration to spot when workflows started running slower.
Filter by Failed state when workflows stop working unexpectedly. The error messages in failed entries often reveal configuration issues or bad input data.
Review execution patterns to understand workflow usage. Frequent executions might indicate scheduling issues or unnecessary manual runs.
Use history to track down data quality problems. If outputs suddenly change, compare recent runs to identify when the issue started.
History Retention
Atlas stores workflow history automatically. This ensures you can review executions from any point in the workflow's lifetime.
History entries include complete output data from each block. This allows full result inspection for debugging and verification.
Best Practices
Check history regularly for failed executions to catch issues early. Set up a routine to review failed runs at least weekly for critical workflows.
Use execution duration as a performance baseline. Sudden increases in run time often indicate data growth or degraded performance.
Filter by user to audit who runs workflows. This helps understand workflow usage patterns and identify training needs.
Keep track of the Triggered by field to distinguish between manual runs, scheduled executions, and other triggers.