The status of a scheduler job signifies the job condition at a certain point in the job’s life cycle. A job can be only in one status at a time. A job can be in any of the six job statuses outlined in the table below.
Job Statuses
Status |
Meaning |
Starting |
The job is currently being started. The status starting is possible when a JMS message was sent to trigger the job but the job has not yet received it. This delay in the JMS message receipt is possible if currently there are not enough threads to run a job. |
Running |
The job is currently performing its unit of work. |
Completed |
The job has finished its unit of work. |
Error |
The job has completed its unit of work but threw an exception during execution, or it is clear that the job has failed due to certain problems. |
Unknown |
The state of the job is not known. The status unknown is possible when a node, during its start up, detects that there are jobs currently running on it. |
Canceled |
The execution of the job was canceled while the job was in status Starting.
If you try to cancel a job in status running, it gets canceled cooperatively. The job acknowledges the request for cancellation but may or may not get canceled. ■ If the job gets canceled, it changes its status from running to either completed, or error. The job does not change to status canceled. ■ If the job does not get cancelled, it remains in status running. |
The figure below shows the possible job statuses and their transitions.
Job Statuses
If a job instance fails to complete four times in a row, the corresponding scheduler task is put on hold.