Status transition diagram - CloudOps Orchestration Service

The initial status of a created execution is Started. The execution may go through multiple statuses before it enters a final status. The following figure shows the status transition process of an execution.

Status description

Status	Description
Started	The execution is started. After an execution is created, it enters this status immediately.
Queued	The execution is waiting in the queue due to traffic control. In most cases, the executions that you start skip this status and directly enter the Running status.
Running	The execution is running.
Success	The execution is complete, and the result is successful.
Failed	The execution is complete, but the result indicates a failure.
Cancelled	The execution is canceled.
Waiting	The execution is waiting for inputs from external systems. If an ACS::TimerTrigger action is defined in the template that is used to create the execution, the execution status changes to Running after the specified point in time arrives. If an ACS::EventTrigger action is defined in the template that is used to create the execution, the execution status changes to Running after a predefined system event occurs. If an ACS::AlarmTrigger action is defined in the template that is used to create the execution, the execution status changes to Running after the threshold of a metric specified in the action is reached. If an ACS::Approve action is defined in the template that is used to create the execution, the execution status changes to Running after the execution is approved by a user who has the permissions to approve the execution.

Note

Final statuses include Success, Failed, and Canceled. In such statuses, the execution is complete, and no subsequent execution is performed.