sift $create_content event rejected: missing $user_id field

Not specified by the original author.

TL;DR

Sift content abuse workflows key every event to a user, so a content event without the user id field is rejected outright and that content never gets scored. Add a stable user id to every content event at the point of creation, including imported and API created content, and decide an explicit strategy for guest content, for example a prefixed session identifier your team agrees on with Sift. Then validate payloads client side so a missing id fails in your logs, not silently at Sift.

sift $create_content event rejected: missing $user_id field

Use this when

• Sift returns a validation error naming the missing user id on content events.
• Content created through an API, import, or admin tool bypasses scoring.
• Guest or anonymous posts exist in your product.

Not for this skill when

• The event is a payment transaction. Use the transaction event schema, not the content schema.
• The user id is present but the decision is wrong. That is workflow tuning, not event structure.

Steps

1. Reproduce with one failing event payload captured from your logs and confirm the user id field is absent or null in the raw JSON. Verify: the captured payload shows the field missing.
2. Trace where that content type is created in your code and add the author user id at creation time for web, mobile, API, and admin paths. Verify: every creation path emits the field in a test event.
3. Define the guest strategy with your team: either require an account before posting, or send a clearly prefixed guest identifier and a matching workflow treatment in Sift. Verify: the chosen strategy is written down and the workflow matches it.
4. Add a client side schema check for required Sift fields that logs and drops bad events with an alert instead of sending them. Verify: a staged event missing the field is caught by your validator.
5. Backfill recent unscored content by resending corrected events for items still live on your platform. Verify: the console shows scores for previously rejected items.

Variant phrasings

sift content event missing user id

Field phrasing without special characters.

sift create content validation error user

Validation phrasing.

anonymous content not scored by sift

Guest content phrasing.

Compatibility: Sift content abuse integration for posts, listings, messages, and reviews. Field names follow the Sift events API spec for your integration version, so check the spec version your SDK targets.

Why it happens

Content workflows build features around the author: account age, prior decisions, linked accounts. Without the author identifier there is nothing to attach the event to, so Sift rejects it at validation instead of scoring it in a vacuum. Creation paths added later, imports, admin tools, partner APIs, are the ones that forget the field.

Edge cases / pitfalls

• Merging guest activity into a registered account later needs an explicit link event, or the history stays split.
• Do not invent random user ids per event to pass validation. That poisons velocity and linking features.
• Deleted accounts still need a stable tombstone id on their old content events, or resends will fail again.

Provenance

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

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

Thread query: sift $createcontent event rejected: missing $userid field

TL;DR: Sift content abuse workflows key every event to a user, so a content event without the user id field is rejected outright and that content never gets scored. Add a stable user id to every content event at the point of creation, including imported and API created content, and decide an explicit strategy for guest content, for example a prefixed session identifier your team agrees on with Sift. Then validate payloads client side so a missing id fails in your logs, not silently at Sift.

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.

Not specified by the original author.

TL;DR

The 400 body names the invalid field, so start there instead of guessing. Validate the required fields for your event type and their types against the Sift events reference. The usual culprits are a wrong $type value, a missing required field, or a nested object where Sift expects a string.

sift api error 400 invalid event structure on decisions api

Use this when

• The Decisions API returns 400 with an invalid event structure message.
• You are sending a new event type for the first time.
• The error names a specific field.

Not for this skill when

• The status is 401 or 403. That is a credentials problem.
• The Score API rejects the event. Validate against the Score API schema instead.
• The event is accepted but the decision looks wrong. That is a workflow problem.

Steps

1. Log the full 400 response and note the field it flags. Verify: you can quote the exact field name.
2. Check the $type value matches a documented Sift event type exactly. Verify: the type string matches the reference, including the $ prefix.
3. Confirm every required field for that event type is present. Verify: $user_id and the other required fields exist in the payload.
4. Check field types: strings where strings are expected, numbers where numbers are expected, no nested objects in flat fields. Verify: each flagged field now matches the schema.
5. Resend the corrected event. Verify: the API returns 200 with a decision.

Variant phrasings

sift decisions api 400 bad event

Shorter phrasing.

sift invalid event structure error

Error-text phrasing.

sift event validation failed decisions

Validation-focused phrasing.

Compatibility: Sift Decisions API; event schema follows the Sift events reference. Applies to server-side event sends.

Why it happens

Sift validates events strictly against per-type schemas before scoring. A typo in $type, a missing required field, or a wrong JSON type fails validation immediately. The 400 is precise about the problem, which makes this a fast fix once you read the body.

Edge cases / pitfalls

• Reserved fields starting with $ have exact names. A near-miss like user_id without the $ is a different, invalid field.
• Some fields are required only for certain event types. Check the schema for your specific type, not the generic one.
• Client libraries sometimes serialize empty objects for unset fields. Omit unset fields instead of sending empty objects.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hLr1Hn94R11vGvLZXU-ZtQ

Resolved from the public thread: https://vectle.com/posts/pst_hLr1Hn94R11vGvLZXU-ZtQ

Thread query: sift api error 400 invalid event structure on decisions api

TL;DR: The 400 body names the invalid field, so start there instead of guessing. Validate the required fields for your event type and their types against the Sift events reference. The usual culprits are a wrong $type value, a missing required field, or a nested object where Sift expects a string.