openlineage event failed error "facet validation error: missing run id"

Not specified by the original author.

TL;DR

Fix the event at the emitter: the run facet is missing its run id, so set the run id in the OpenLineage client configuration or the integration environment and confirm the job and run identifiers are generated before the event is sent. OpenLineage validates events against the schema on the collecting side. An event whose run facet carries no run id cannot be attached to a job run and is rejected as invalid.

openlineage event failed error "facet validation error: missing run id"

Use this when

• The check or run fails with this symptom: an OpenLineage event fails with facet validation error missing run id.
• You are working on an OpenLineage integration emitting run events from a pipeline or a custom client and the failure repeats on the same data or configuration.
• You need the failing rows, rule, or stage isolated before changing thresholds or code.

Not for this skill when

• An event rejected for a different facet, such as a malformed dataset facet, where the run id is present and valid.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Capture one rejected event payload and inspect the run section. Verify: the run id field is empty or absent in the actual payload
2. Check how the integration creates the run: automatic generation in the client, or an id the caller must supply. Verify: the missing generation step is identified
3. Set a stable run id per execution in the client or integration configuration, reusing the orchestrator run identifier where one exists. Verify: emitted events carry the same run id across start and complete events
4. Emit a test event and validate it against the collector. Verify: the event is accepted and the run appears in the lineage backend
5. Confirm start and complete events for one real run share the id. Verify: the run shows both events in the backend

Variant phrasings

openlineage facet validation error missing run id

The shorter phrasing focused on the named failure.

openlineage event failed missing run id

The symptom phrasing a searcher tries next.

openlineage run facet validation fix

The variant naming the failing stage or tool directly.

Compatibility: OpenLineage 1.x client libraries and integrations, Marquez and compatible backends

Why it happens

Some integrations only generate a run id when the client is initialised through their lifecycle hooks. A hand-built client, a custom emitter, or an upgrade that changed the initialisation order can send events whose run facet is present but empty, and schema validation rejects them.

Edge cases / pitfalls

• Start and complete events with different run ids create two half runs in the backend; generate the id once per execution and pass it through.
• A proxy or collector that strips unknown fields can remove the run id in transit; validate at the collector, not only at the emitter.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_soy4MNSNzTJykykXro3avQ

Resolved from the public thread: https://vectle.com/posts/pst_soy4MNSNzTJykykXro3avQ

Thread query: openlineage event failed error "facet validation error: missing run id"

TL;DR: Fix the event at the emitter: the run facet is missing its run id, so set the run id in the OpenLineage client configuration or the integration environment and confirm the job and run identifiers are generated before the event is sent. OpenLineage validates events against the schema on the collecting side. An event whose run facet carries no run id cannot be attached to a job run and is rejected as invalid.