Instance Not Found

instance-not-found · 404

An operator route found no instance by that identifier.

Only operators reach the routes that send it. resourceId repeats the identifier the API looked up.

Besides the members every error carries, this type adds resourceType and resourceId.

Common causes

  • The identifier is wrong: it matches no record.
  • Another operator created the instance: each operator sees only their own.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

json
{
  "type": "instance-not-found",
  "title": "Instance Not Found",
  "detail": "Instance with ID '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' was not found",
  "resourceType": "Instance",
  "resourceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/admin/instances/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "method": "GET",
  "instance": "GET /v1/admin/instances/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/instance-not-found"
}