Run history
Viewing logs and outcomes for past workflow job executions.
The Run history page (/jobs) lists every Job created in your workspace. Use it to find a specific run, diagnose failures, and inspect what each node produced.
Reading the list
Each row represents one Job — one execution of a Workflow. The columns show:
| Column | What it shows |
|---|---|
| Workflow | The Workflow that ran |
| Status | COMPLETED, WAITING, or a failure status |
| Started at | When the Job began (startedAt) |
| Duration | Total wall-clock time the execution took |
Common statuses
- COMPLETED — every node ran successfully and the Job is closed.
- WAITING — a node paused execution pending an external event (e.g. a WAIT_FOR_EVENT or SLACK_APPROVAL node). The Job remains open until the event arrives. See Wait & resume.
Drilling into a Job
Click a row to open the Job detail view.
The detail view lists every Action that executed — one row per node. For each Action you can see:
- Node type — the
moduleTypeof the node that ran (e.g.SEND_WHATSAPP,LLM_COMPLETION,CONDITIONAL) - Status — whether the individual node succeeded or failed
- Payload — the serialised input data the node received
- Output — the data the node produced for downstream nodes
- Timing —
startedAt,finishedAt, anddurationfor this node alone
Retries
When a node fails, EzFlow records a FailedItem attached to the Job. The FailedItem tracks the error details and retry state — including the current attempt count, the maximum number of attempts, and when the next retry is scheduled (nextRetryAt). Each retry attempt is logged separately so you can see the full history of attempts for a given failure.
Related
- Job & action model — full field reference for Job and Action records
- Wait & resume — how WAITING Jobs pick back up after an event arrives
- Executions & Jobs — conceptual overview of how a run works