Skip to content
Error codes · Monitors, checks & agents

RU-3003: Monitor not found

No monitor with that ID exists in this account. Monitors belonging to other accounts answer exactly the same way, so this code cannot confirm whether an ID exists elsewhere.

Where it is raised

  • Checks: 8 routes
  • Status Pages: 1 route
  • Errors: 1 route
  • Agents: 4 routes
  • Agent maintenance windows and agent metrics exports, where the text says Agent not found
  • The GitHub App installation routes, where the text says No GitHub App installation with that id belongs to this account

What triggers it

The route looks the id up inside the caller's own account only. An id from another account and an id that never existed take the same branch and send the same text. On a status page component create, a monitor id that does not belong to the account answers this code too.

Example response

GET /api/v1/checks/{id}
HTTP 404

{
  "error": "Monitor not found.",
  "code": "RU-3003"
}

Common causes

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

How to fix it

  1. List your monitors (GET /api/v1/checks) and confirm the ID.
  2. Confirm the API key belongs to the account that owns the monitor.