Jobs & Actions
Jobs & Actions
Background jobs and action queues that execute workflow steps asynchronously.
Every time a Workflow runs, EzFlow creates a Job to track the full execution. Within that Job, each node that executes produces an Action — a per-step record with its inputs, outputs, and timing.
Job and Action at a glance
| Record | What it represents |
|---|---|
| Job | One complete execution of a Workflow. Has a status, start and finish times, and links to its Workflow and all its Actions. |
| Action | One node's execution within a Job. Captures the node type, input payload, output, and per-node timing. |
A Job moves through statuses as execution progresses. The two most common outcomes are COMPLETED (every node ran successfully) and WAITING (a node paused execution pending an external event). See Executions & Jobs for an overview of how a run works.
What you can do
- Browse past runs — filter and search Jobs by Workflow, status, and date at
/jobs. See Run history. - Inspect node-level detail — open a Job to see every Action: what each node received, what it produced, and how long it took.
- Understand the data model — learn the fields on Job and Action records, the outbox pattern used for reliability, and how retries work. See Job & action model.
- Learn about wait & resume — when a node pauses execution, EzFlow snapshots the run and resumes it when the awaited event arrives. See Wait & resume.
Related
Run history
Browse and filter past Workflow runs and drill into per-node results.
Job & action model
Field reference for Jobs, Actions, and the outbox pattern.
Wait & resume
How paused Workflows snapshot their state and resume when an event arrives.
Executions & Jobs
Conceptual overview of how a Workflow run progresses from trigger to completion.