Job status
When a Job is invoked, a status is returned. The status provides information about the result of the Job and other related details.
Table provides information about the different job statuses along with a description of each status.
| Job status | Description |
|---|---|
| CANCELED_BEFORE_START | The Cancel command was received and was processed successfully before the Job moved out of the NOT_STARTED state. |
| CANCELED_WHILE_RUNNING | A Cancel command was received and processed successfully while the Job was in the RUNNING state. |
| COMPLETED_WITH_WARNINGS | The Job completed with partial success, with some subtasks completed successfully, and some others failed. Manual intervention is required either to complete the intended task or to revert the system to its original state. For further details, see the JobResponse.Progress.CompletedTasks for the Job. |
| COMPLETED_WITH_ERROR | The Job ended naturally. However, due to one of
the following conditions listed below, the Job was not moved to
COMPLETED_OK state.
|
| FAILED_TO_START | The Job could not be started due to an unexpected internal error in the Job processing. |
| FAILED_BEFORE_COMPLETION | The Job did not complete. This usually means that the Job method threw an exception or was interrupted, without the Cancel command. |
| NOT_STARTED | The Job has not yet been initiated by the
framework. Note: If a Job remains in this state for a significant
amount of time, you might want to check what is causing the
delay in initiating the Job.
|
| RUNNING | The Job is in progress. |
| FAILED_BEFORE_COMPLETION_RETRY | The Job cannot perform the requested operation. The virtual I/O server (VIOS) is busy performing other tasks. Try the operation after some time. |
| COMPLETED_OK | The Job completed successfully and subsequent user
intervention is not required. Note: The Job might still have issued
warnings and there might still be some minor cleanup
required.
For further details, see the
JobResponse.Progress.CompletedTasks for the
Job. |
