Skip to content
Error codes · Status pages & incidents

RU-5002: Incident not found or not creatable

Either no incident with that ID exists in this account, or an incident could not be created because the status page, check, component relationship, or region named in the request don't line up under your account.

On the wire

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

Common causes

  • The check is not a component of the named status page.
  • The region named is not one the check is monitored from.
  • The ID belongs to another account, or the incident was deleted.

How to fix it

  1. List your status pages and checks over the API and confirm every ID belongs to this account.
  2. Confirm the check is attached to the status page as a component.
  3. Confirm the region is one of the check's monitored regions.

Related codes

  • RU-5003: Incident conflicts with live outage state

Still stuck?

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