Package version
Cancellation has been requested for the job.
Following cancellation request, the job is now successfully canceled.
Job completed successfully. This reflects that both the job itself and output collection states completed successfully
Job failed.
Job is completed in the target. It is in output collection state now.
When heartbeat is enabled, if the run isn't updating any information to RunHistory then the run goes to NotResponding state. NotResponding is the only state that is exempt from strict transition orders. A run can go from NotResponding to any of the previous states.
Run hasn't started yet.
The job is paused by users. Some adjustment to labeling jobs can be made only in paused state.
The run environment is being prepared.
(Not used currently) It will be used if ES is creating the compute target.
The job is queued in the compute target. For example, in BatchAI the job is in queued state, while waiting for all required nodes to be ready.
The job started to run in the compute target.
The job is in a scheduled state. Job is not in any active state.
Run has started. The user has a run ID.
Default job status if not mapped to all other statuses
Generated using TypeDoc
Known values of JobStatus that the service accepts.