Interpreting Pipeline and Component Health State
Each pipeline and component within that pipeline returns a health status of
HEALTHY, ERROR, "-", No Completed
Executions, or No Health Information Available. A pipeline
only has a health state after a pipeline component has completed its first execution
or if component preconditions have failed. The health status for components
aggregates into a pipeline health status in that error states are visible first when
you view your pipeline execution details.
Pipeline Health States
HEALTHY-
The aggregate health status of all components is
HEALTHY. This means at least one component must have successfully completed. You can click on theHEALTHYstatus to see the most recent successfully completed pipeline component instance on the Execution Details page. ERROR-
At least one component in the pipeline has a health status of
ERROR. You can click on theERRORstatus to see the most recent failed pipeline component instance on the Execution Details page. No Completed ExecutionsorNo Health Information Available.-
No health status was reported for this pipeline.
Note
While components update their health status almost immediately, it may take up to five minutes for a pipeline health status to update.
Component Health States
HEALTHY-
A component (
ActivityorDataNode) has a health status ofHEALTHYif it has completed a successful execution where it was marked with a status ofFINISHEDorMARK_FINISHED. You can click on the name of the component or theHEALTHYstatus to see the most recent successfully completed pipeline component instances on the Execution Details page. ERROR-
An error occurred at the component level or one of its preconditions failed. Statuses of
FAILED,TIMEOUT, orCANCELEDtrigger this error. You can click on the name of the component or theERRORstatus to see the most recent failed pipeline component instance on the Execution Details page. No Completed ExecutionsorNo Health Information Available-
No health status was reported for this component.
