Skip to main content

Job States

During their life-cycle, jobs transition among the following states:

SUBMITTED

The job has been created but hasn't been scheduled for execution yet.

PROCESSING

Job is being processed.

QUEUED

The job has been processed and enqueued for execution.

STARTING

The job execution is starting.

DOWNLOADING_INPUT

BatchX has provisioned a new machine for running the job container, and is copying the job input data to it from the environment file-system.

RUNNING

Job container is running. From this point container stderr and stdout can be received as job logs.

UPLOADING_OUTPUT

Container execution has finished and BatchX has started uploading the job output files to the environment file-system.

CANCELLING

The job has received a cancellation request, but cancellation has not been confirmed yet.

SUCCEEDED

The job has been successfully executed.

WARNING

The job has been successfully executed but with warnings. bx run exit code will still be 0, so the curse of client workflow is not broken.

FAILED

The job has terminated with errors.

CANCELLED

The job has been cancelled.

OUT_OF_MEMORY

The job has been killed due an out of memory error. This means that the memory specified for the job was not high enough.

INVALID_OUTPUT

The job has generated an invalid output. This error means that the image is faulty and needs to be fixed.

<cached>

The job execution has been skipped, and the output has been generated from a past equivalent job. See Execution caching for more details.