Where it is raised
POST /api/v1/incidentsPOST /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
- List your status pages and monitors over the API and confirm every ID belongs to this account.
- Confirm the monitor is attached to the status page as a component.
- Confirm the region is one of the monitor's monitored regions.