Chapter 9. Job States
You can view the state of any job from the Workflow Manager dashboard, to determine whether the job started, succeeded, failed, and so forth.
A workflow, coordinator, or bundle job can be in any of the following states:
- Prep
When a workflow, coordinator, or bundle job is first submitted, it is in the Prep state, meaning the job is defined and saved, and a unique ID is assigned to it, but the job is not running.
Jobs can transition from Prep to Running or Killed states.
- Running
When a workflow, coordinator, or bundle job is executed, it goes into the Running state. A job remains in the Running state as long as it does not reach its end state, does not end in error, or is not suspended.
Jobs can transition from Running to Succeeded, Suspended, Killed, or Failed states.
- Suspended
A running workflow, coordinator, or bundle job can be suspended. The job remains in Suspended state until the job is resumed or is killed.
Jobs can transition from Suspended to Running or Killed states.
- Succeeded
A running workflow, coordinator, or bundle job transitions to the Succeeded state when it reaches the end node. it final state.
Succeeded is a final state, so it does not transition to other states.
- Killed
When a workflow, coordinator, or bundle job is killed manually or by reaching a kill node in the workflow, the job transitions to the Killed state.
Killed is a final state, so it does not transition to other states.
- Failed
When a running workflow, coordinator, or bundle job fails due to an unexpected error, it transitions to the Failed state.
Failed is a final state, so it does not transition to other states.
More Information