Job
Identifies the workload.
How a workload moves from acceptance to a terminal outcome.
The execution lifecycle exposes the state of work as it is queued, routed, assigned, processed, completed, failed, or retried.
The canonical successful path.
01queued
02routing
03assigned
04running
05completed
Queued means the workload has entered execution state. Routing means the network is evaluating eligible capacity. Assigned means a destination has been selected. Running means processing is active. Completed means execution has reached a successful terminal state and the result can be exposed.
Failures remain visible instead of being collapsed into generic errors.
01running
02failed
03retrying
04routing
05assigned
06running
Where retry behavior is available, retrying represents a deliberate new attempt within the execution lifecycle. It should not erase the history of the earlier failure.
Interpret status together with execution context.
Workflow Run
Explains orchestration around the workload.
Assignment
Shows selected execution capacity when routing has completed.
Timing
Shows where execution time was spent.
Logs & telemetry
Provide operational evidence around running or failed work.
Result or failure
Represents the terminal outcome.