Skip to content
Error codes · realuptime errors ingest

RU-4006: Errors project or issue not found

No errors project or issue with that ID exists in this account. Resources in other accounts answer the same way.

Where it is raised

  • GET /api/v1/errors/projects/{id}
  • GET /api/v1/errors/projects/{id}/issues
  • GET /api/v1/errors/issues/{id}
  • PATCH /api/v1/errors/issues/{id}
  • POST /api/v1/errors/releases
  • Keyed MCP endpoint, Errors tools

What triggers it

The project, issue or release is looked up inside the caller's account. For a release the message is No errors project with that ID exists in this account. A project id that is not a UUID is a RU-4007 refusal first.

Example response

GET /api/v1/errors/projects/{id}
HTTP 404

{
  "error": "Project not found.",
  "code": "RU-4006"
}

Common causes

  • The project or issue was deleted.
  • The ID belongs to a different account.
  • A typo in the ID.

How to fix it

  1. List your projects (GET /api/v1/errors/projects) and confirm the ID.
  2. Confirm the API key belongs to the account that owns the resource.