Monitor workflow runs
How to read ZenAdmin's workflow run history — statuses, failure reasons, retrying failures, forcing stuck runs, and tracing one execution node by node.
A workflow's detail page opens on Workflow Triggers — its run history.
The numbers and the list
Stat tiles count total triggers and how many were Successful, In-progress, Failed or Cancelled. Below, the Workflow History table lists each run — searchable, filterable and exportable:
- Triggered For — the person the run was for, with their work email underneath (or their employee ID if they have no work email).
- When it started and completed, and its status.
- Reason — why a run failed or was cancelled. Shows - when there's nothing to report.
Trace a single run
Click the eye icon on a run's row to open the flow diagram for that one run. Each node shows its status (including skipped branches), and you can open any node for a read-only view of its configuration. This is your debugger: walk the path the run actually took.
When a run failed or was cancelled, a Workflow failed or Workflow cancelled banner sits at the top. Open the node where it stopped to see Error details or Cancellation details — click Copy details to paste them into a support request.
Acting on a run
From a run's row:
- Retry — re-run a Failed or Cancelled run.
- Force Execute — push an in-progress run that's stuck waiting at its trigger.
- Cancel Trigger — stop a run.
Each action confirms before doing anything.
Don't see these actions?
Run actions only appear for people who can edit workflows, and only while the workflow is Active. A node that was cancelled can't be skipped.
The audit trail
The Audit History tab records the workflow's own life — created, edited, nodes added or removed, activated, deactivated, triggered — so "who changed the offboarding flow" always has an answer.
Last updated on