Restore Not Found

restore-not-found · 404

The API found no restore by that id in the workspace the call ran in.

resourceId repeats the id the API looked up. The service in the path is checked first, so one the workspace doesn't hold answers service-not-found instead.

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

Common causes

  • The id isn't the restoreId the restore call answered with.
  • The restore was started in another workspace than the one the call ran in.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • Use the restoreId from the answer to the restore call.
  • Send X-Ghaym-Workspace with the workspace the restore was started in.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

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