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. Each entry shows when the workflow ran and who initiated the execution.
Understanding History Entries
Each history entry displays key information about the execution. The timestamp shows how long ago the workflow ran using relative time like "1 second ago" or "2 hours ago".
The duration indicates total execution time in seconds. This helps identify performance issues or unusually slow runs.
The user attribution shows who triggered the execution. Manual runs display the user's name while scheduled executions show "System" or the schedule name.
Filtering by State
Use the state filter dropdown to show only executions with specific outcomes. This helps quickly find failed runs or monitor successful executions.
- 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
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.
Check the state filter for failed runs 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.
Managing History Entries
Delete individual history entries by clicking the X button next to the entry. This removes the record but does not affect the workflow itself.
History entries consume storage space proportional to the output data size. Delete old entries periodically to free up space.
Deleting a history entry is permanent and cannot be undone. Make sure you no longer need the execution results before removing entries.
History Retention
Atlas stores workflow history indefinitely by default. This ensures you can review executions from any point in the workflow's lifetime.
Large workflows with frequent executions accumulate substantial history data. Monitor your storage usage if you run data-intensive workflows often.
History entries include complete output data from each block. This allows full result inspection but increases storage requirements compared to execution logs alone.
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.
Document significant workflow changes by noting them alongside history entries. This helps correlate execution behavior with configuration changes.
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 successful history entries from important runs as documentation. These serve as reference points showing expected outputs and behavior.
