Automations → Execution History lists runs, 25 a page. Filter by workflow name, status (Completed, Failed, Running, Waiting, Skipped) and dates.
Statuses
Completed, Failed, Running, Waiting (a durable delay or event wait), Skipped (rate control). When a wait resumes, the original row is set to Completed and the continuation is a new row; so Completed on a parent does not mean the workflow finished. An event wait with an expiry date never expires on its own and stays Waiting, counting against "max concurrent".
What is not recorded
Runs stopped by the loop guard, by a missing plan feature, or because the workflow was not active leave no row at all.
Actions
- View Details shows each step's id, type, status, duration, error and output (the input is visible only in the editor's "Recent executions" panel).
- Re-run runs the whole workflow again with the same data, using the original snapshot. Invoice, estimate, booking, enrollment and announcement actions do not duplicate; email, SMS, webhooks and CRM actions do.
- Retry from failed step appears for Failed runs and reuses earlier outputs. It needs a snapshot, an identifiable failed step that is not inside a parallel block, and the workflow still Active.
Neither asks for confirmation. Both also count towards the loop guard.