Backup Not Found

backup-not-found · 404

The database in the path has no backup by that id.

A backup is found only under its own database, and resourceId repeats the id the API looked up. A database the workspace doesn't hold answers service-not-found first.

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

Common causes

  • The backup is of another database than the one in the path.
  • The backup was deleted.
  • The id has a typo in it.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • List the database's backups with GET /v1/services/<service>/backups and take the id from that answer.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

json
{
  "type": "backup-not-found",
  "title": "Backup Not Found",
  "detail": "Backup with ID '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402' was not found",
  "resourceType": "Backup",
  "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/backups/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/restore",
  "method": "POST",
  "instance": "POST /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/backups/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/restore",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/backup-not-found"
}