OCI Batch Lifecycle States Reference

Following are the lifecycle states of a batch context:

• CREATING: Initial state after you create a batch context. The create batch context workflow runs. If it succeeds, the state changes to ACTIVE. If it fails, the state changes to FAILED.

• ACTIVE: The batch context is available and accepts new jobs. You can update or delete the batch context. Updates that require an asynchronous workflow change the state to UPDATING. Updates such as display name or tags keep the state ACTIVE.

• INACTIVE: The batch context is deactivated and doesn't accept new jobs. You can reactivate the batch context to return to ACTIVE or delete the batch context to move to DELETING.

• UPDATING: The system is applying configuration changes through an asynchronous workflow. If it succeeds, the state changes to ACTIVE. If it fails, the state changes to NEEDS_ATTENTION.

• NEEDS_ATTENTION: A validation or update failed. Correct the configuration or dependent resources. After a successful validation or update, the state changes to ACTIVE.

• DELETING: The system is deleting the batch context and dependent resources through an asynchronous workflow. On success, the state changes to DELETED.

• DELETED: Terminal state. The batch context is removed and quota is released. On success, the workflow sets the state to DELETED.

• FAILED: The create batch context workflow failed. The work request includes error details. You can't and shouldn't delete a batch context in a failed state. It's a terminal state.

• ACTIVE: The Job Pool is available for standard operation.
• INACTIVE: The Job Pool is paused. You can't submit new jobs while the pool is INACTIVE.

• UPDATING: The system is applying configuration changes through an asynchronous workflow. If it succeeds, the state changes to ACTIVE. If it fails, the state changes to NEEDS_ATTENTION.

• NEEDS_ATTENTION: A validation or update failed. Correct the configuration or dependent resources. After a successful validation or update, the state changes to ACTIVE.

• DELETED: The Job Pool no longer exists. This is a terminal state.

In the following list:

• States are presented in the format Lifecycle State / Lifecycle Details.
• Angle-bracket values such as <type> are placeholders you replace with a specific error category.

Lifecycle States

• ACCEPTED: The system accepted the create request.

• ACCEPTED/VALIDATING: The system accepted the create request and is validating the job input.

• ACCEPTED/VALIDATED: Validation succeeded. The job is ready to be processed.

• WAITING: The job is waiting to start.

• IN PROGRESS: When any task enters IN PROGRESS, the job also enters IN PROGRESS.

• SUCCEEDED: The job completed successfully.

  Note
  
  A job reaches SUCCEEDED when all its tasks have SUCCEEDED.

• FAILED/FAILURE DETAILS: The job failed. If any job reaches this state, the job transitions to FAILED.

• FAILED/VALIDATION FAILED: Validation didn't pass. The job won't run.

• CANCELING/SCHEDULED: The system accepted a cancel request and scheduled cancellation.

• CANCELING/IN PROGRESS: The system is canceling the job.

• CANCELED: The job or task stopped before completion because of cancellation.

• WAITING/PAUSED: The user paused the job before it started running. The system preserves the previous state for resume.

In the following list:

• States are presented in the format Lifecycle State / Lifecycle Details.
• Angle-bracket values such as <type> are placeholders you replace with a specific error category.

Lifecycle States

• ACCEPTED: The system accepted the create request.

• WAITING/DEPENDENCY: A task can't run yet because a prerequisite in its DAG hasn't completed.

• WAITING/QUEUED: A task is ready and placed in the scheduling queue.

• WAITING/ASSIGNING: The scheduler is selecting an execution node for the task.

• WAITING/ASSIGNED: The task is assigned to a node and is waiting to start.

• WAITING/PAUSED: If job is paused by the user then the task will be paused. The system preserves the previous state for resume.

• IN PROGRESS: The node agent started running the task. When any task enters IN PROGRESS, the job also enters IN PROGRESS.

• SUCCEEDED: The task completed successfully. A job reaches SUCCEEDED when all its tasks have SUCCEEDED.

• CANCELED: The task stopped before completion because of cancellation.

• ACTIVE: The Batch Task Profile is available for standard operation.
• DELETED: The Batch Task Profile no longer exists. This is a terminal state.

• ACTIVE: The Batch Task Environment is available for standard operation.
• DELETED: The Batch Task Environment no longer exists. This is a terminal state.