Interpreting Pipeline Status Details - AWS Data Pipeline

Interpreting Pipeline Status Details

The various status levels displayed in the AWS Data Pipeline console and CLI indicate the condition of a pipeline and its components. The pipeline status is simply an overview of a pipeline; to see more information, view the status of individual pipeline components. You can do this by clicking through a pipeline in the console or retrieving pipeline component details using the CLI.

Status Codes


The component or resource is being started, such as an EC2 instance.


The component was canceled by a user or AWS Data Pipeline before it could run. This can happen automatically when a failure occurs in a different component or resource that this component depends on.


The component or resource was canceled as a result of a cascade failure from one of its dependencies, but the component was probably not the original source of the failure.


The pipeline is being deactivated.


The component or resource encountered an error and stopped working. When a component or resource fails, it can cause cancelations and failures to cascade to other components that depend on it.


The component completed its assigned work.


The pipeline was deactivated.


The component was paused and is not currently performing its work.


The pipeline is ready to be activated for the first time.


The resource is running and ready to receive work.


The resource is scheduled to run.


The resource is shutting down after successfully completing its work.


The component skipped intervals of execution after the pipeline was activated using a time stamp that is later than the current schedule.


The resource exceeded the terminateAfter threshold and was stopped by AWS Data Pipeline. After the resource reaches this status, AWS Data Pipeline ignores the actionOnResourceFailure, retryDelay, and retryTimeout values for that resource. This status applies only to resources.


The pipeline definition is being validated by AWS Data Pipeline.


The component is waiting for its worker client to retrieve a work item. The component and worker client relationship is controlled by the runsOn or workerGroup fields defined by that component.


The component is verifying that its default and user-configured preconditions are met before performing its work.