Execution health · rule lineage-job-failing
Pipeline jobs whose latest run failed
A Metacenta review checks this under the rule Every job's latest recorded run succeeded. Everything below applies whether or not you ever commission one.
What this rule checks
From an export of OpenLineage events, this rule flags each job whose most recent recorded run ended in FAIL or ABORT. It names the datasets that job writes.
Why it matters
Whatever the job produces may be stale or partly written. Anything that reads those datasets carries the problem forward.
How to fix it
Fix the jobs whose latest run failed. Check whether the job has run successfully since the export. If not, fix it before anything reads its outputs.
When it is fine to leave
If the job has succeeded since the export was taken, the finding is out of date. Send a newer export, or tell us, and it comes out of your report.
What we need to check it
An export of OpenLineage events, such as a JSON Lines file from your lineage backend. The finding describes the export, so it is only as recent as the events in it.