This article describes the meaning and flow logic of each Status during the execution of a Volcano Engine CP pipeline, helping you better monitor and manage pipeline Execution status. ## Background The Status of a pipeline reflects its entire life cycle from trigger to completion. Understanding the meaning of each Status helps with: * **Troubleshooting**: Quickly identify the reason why the pipeline is stuck or has failed * **Optimize efficiency**: Identify resource bottlenecks and adjust the concurrency policy * **Automate operations**: Set up alerts and notifications based on Status changes ## Status description CP pipelines use an asynchronous scheduling mechanism. After a pipeline is triggered, it goes through multiple stages such as resource scheduling, lock contention, and execution, with each stage corresponding to a different Status. |**Console copy** |**API Status** |**Description** | |---|---|---| |**In queue** |Enqueued |The pipeline trigger request has been submitted and is waiting for the scheduling system to allocate execution resources. At this time, the pipeline has not yet begun actual execution. | |**Environment starting** |Dequeued |The pipeline has been removed from the wait queue and is preparing the execution environment or waiting for dependencies to become available. | |**waiting for lock** |LockWaiting |The pipeline is waiting to obtain a resource lock to prevent conflicts caused by multiple pipelines concurrently performing actions on the same resources.

tip

Resource lock is a concurrency control mechanism that ensures that at any given time only one pipeline instance can access or operate specific shared resources. When multiple pipelines are triggered simultaneously, only the instance that obtains the lock can continue execution, while other instances enter the waiting for lock status and wait.

| |**Running** |InProgress |The pipeline is running and executing tasks for each stage and step. | |**Canceled** |Canceling/Canceled |The pipeline has been manually canceled or automatically canceled by the system, execution is terminated, and not all tasks are completed. | |**Succeeded** |Succeeded |All steps of the pipeline have been executed successfully, with no errors or exceptions occurring, and the overall execution was successful. | |**Fail** |Failed |A step in the pipeline execution failed or a system error occurred, resulting in overall execution failure. | |**Environment startup timeout** |Timeout |The pipeline exceeded the configured timeout threshold while waiting for the execution environment to start, and the system automatically terminated the execution. | ## Status flow The Status of a pipeline follows fixed flow rules, forming a complete life cycle from the initial Status to the final Status. ![图片](https://portal.volccdn.com/obj/volcfe/cloud-universal-doc/upload_d37851feeb941e8f2d1e377538a10a12.png) ## View pipeline status 1. Log in to the [Continuous Delivery Console](https://console.volcengine.com/cp). 2. In the left navigation bar, select **workspace** and enter the target workspace. 3. In the left navigation bar, select **pipeline** and click the target pipeline name. 4. In the **Run Records** column, view the status of each instance. ## FAQ For methods to handle abnormal statuses in pipelines, see [Pipeline Status FAQ](https://www.volcengine.com/docs/6461/2306537).

Code Pipeline