Skip to content
Error codes · realuptime errors ingest

RU-4011: Feedback event not found

The feedback report's eventId did not match any stored event for this project. Often transient: the event batch it describes is still in flight and has not landed yet, which is why the SDK's transport retries this specific refusal a few times before giving up. Ships with `reason: "event_not_found"`.

On the wire

Ships with HTTP status 404, carrying "code": "RU-4011" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • The report was submitted before its event's batch finished sending.
  • The event's retention window already passed (feedback has no lifetime longer than the event it describes).
  • A hand-rolled client sending an eventId that was never the SDK's own minted id.

How to fix it

  1. Let the SDK's built-in retry run; it is designed for this race.
  2. Confirm the event actually reached ingest (check the issue's occurrences).
  3. Use the official SDK's showReportDialog rather than minting your own eventId.

Related codes

  • RU-4010: User feedback switched off for this project

Still stuck?

Ask support and mention RU-4011: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.