Backup Not Deleted

backup-purge-failed · 502

The place backups are kept didn't confirm it deleted this backup's files, so the API kept the backup's record.

The files go first and the backup's record after, so the backup stays listed. Deleting it again is safe.

Besides the members every error carries, this type adds backupId.

Common causes

  • The place backups are kept was slow, down, or refused the delete at that moment.

How to fix the call

  • Retry the delete after a short wait.
  • If it keeps failing, tell the user the backup is still there, quoting detail.

Example response

json
{
  "type": "backup-purge-failed",
  "title": "Backup Not Deleted",
  "detail": "The backup could not be deleted. Nothing was changed; try again.",
  "backupId": "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",
  "method": "DELETE",
  "instance": "DELETE /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/backups/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402",
  "status": 502,
  "docs": "https://ghaym.me/docs/errors/backup-purge-failed"
}