Skip to content
Error codes · realuptime errors ingest

RU-4008: Referenced previous release not found

POST /api/v1/errors/releases named a `previousRelease` that does not exist yet for this project. Releases link to a release that ALREADY exists (from an earlier announcement or from an event that tagged it); this call never creates the release it points at.

On the wire

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

Common causes

  • A typo in the `previousRelease` version string.
  • Announcing releases out of order: the release being named as "previous" has not shipped an event or been announced yet.

How to fix it

  1. Check the exact release string with GET /api/v1/errors/projects/:id/issues?release=... or the dashboard's Releases section.
  2. Announce releases in shipped order, or omit `previousRelease` and let it infer the most recently seen one.

Related codes

  • RU-4007: Invalid errors API request

Still stuck?

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