Core concepts
Executions & Jobs
How workflow runs are tracked, queued, and inspected.
Every time a Workflow runs — whether from a trigger firing or a manual test — EzFlow creates a Job. A Job is a complete record of that execution: when it started, how long it took, and what every node produced.
The Job and Action model
| Record | What it is |
|---|---|
| Job | One execution of a Workflow. Stores the status, startedAt, finishedAt, and duration, and links back to the Workflow that ran. |
| Action | One node's execution within a Job. Stores the node type (moduleType), status, the input payload, the output, and per-node timing. |
A single Job contains one Action per node that executed. You can inspect both at Run history and in the Job & Action model reference.
How a run works
- The trigger fires and the orchestrator loads the committed DAG snapshot for the active branch.
- Comment nodes (annotation-only nodes used for documentation on the canvas) are stripped out before execution begins.
- The engine executes each node in graph order, injecting each node's output into the input handles of its downstream nodes via the edges.
- A
trackingIdis propagated across all actions in the run so the full execution stays correlated. - When all nodes complete, the Job status is set to COMPLETED.
COMPLETED vs WAITING
The execution engine produces one of two outcomes:
- COMPLETED — every node ran to completion. The Job is closed.
- WAITING — a node paused execution pending an external event — for example, a Wait for Event node waiting for an inbound communication. The engine saves an execution snapshot and the Job remains open. When the awaited event arrives, execution resumes from exactly where it left off. See Wait & resume.
Reliability
EzFlow uses an outbox pattern for persisting Job and Action records, ensuring execution state is durable even if a node fails mid-flight. Failed node executions are captured in a FailedItem record and can be retried.
Related
- Run history — filter and browse past runs
- Job & Action model — detailed field reference for Jobs and Actions
- Wait & resume — how paused runs pick back up after an external event