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, monitor, component relationship, or region named in the request don't line up under your account.

Where it is raised

  • POST /api/v1/incidents
  • POST /api/v1/incidents/{id}/updates

What triggers it

Creation resolves the status page, the monitor as a component of that page, and the region in one step, and any mismatch sends this one text. A templateId from another account answers its own sentence. An incident id that does not exist for posting an update answers Incident not found.

Example response

POST /api/v1/incidents
HTTP 404

{
  "error": "Could not create that incident. Check that the status page and check belong to your account, that the monitor is a component of that page, and that it is monitored from the region you named.",
  "code": "RU-5002"
}

Common causes

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

How to fix it

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

Related codes