Run Status¶
A run status provides context about the progress or results of a batch pipeline execution.
There are six statuses: Pending, Running, Completed, Completed with warnings, Failed, and Missing.
Tip
The status of instances, runs, and tasks are color-coordinated for better visualization. Colors are repeated in tables, Gantt charts, and graphs.
Run Status event¶
The system uses the status property from the Run Status event to identify changes in status for a specified
batch pipeline run.
For more information, see Events.
Status changes¶
Any change in status received by the system updates the run status regardless of the previous status. Run timings are updated as needed.
For example, if the system receives events for a previously completed run (identified by a unique run_key for a batch pipeline), the status, end time, and duration change to reflect the new events.
Statuses¶
| Status | Example situations |
|---|---|
| Running | Run is in progress Tasks and/or tests are in progress |
| Pending | Run has not yet occurred for its expected schedule |
| Missing | Run did not occur during its expected schedule |
| Failed | Run failed X tasks in run are incomplete X tasks in run failed |
| Completed | Run completed successfully. All tasks and/or tests succeeded. |
| Completed with warnings | Run completed but with warnings Tasks and/or tests in run had warnings Tasks and/or tests in run had failures |
Late runs¶
The statuses Running, Failed, Completed, and Completed with warnings are sent with the Run Status event.
The statuses Pending and Missing are set by the system when a run does not align with its expected schedule. In addition to the status, lateness indicators provide context about how a run relates to expectations.
Set component expectations so Observability can generate these details and you can monitor your batch pipelines relative to what you know should happen.
View lateness indicators¶
You can view lateness indicators for batch pipeline runs from the Batch Runs tab of the Events page and above the run details tabs.
Hover your cursor over an indicator for more details.
Set rules for runs¶
You can set rules for batch pipeline components that are included in a journey. When rules are set, Observability can notify you if runs are a certain status, behave unexpectedly, or do not meet their schedule.
Troubleshooting: Pending or Missing Runs