Retry failed backups
Queues failed backups again. The server already retries a failed backup on its own, up to 3 times, within 24 hours of its creation, so a manual retry is rarely needed within that time.
Follow the retried backups with “List backups” (filter[id][]) and read phase. The work finishes later: see Writes and asynchronous operations. Backups that cannot be retried are reported in meta.skipped, each with a reason_code and a message, and do not fail the call: UNSUPPORTED (the backup is not in phase failed), SITE_UNREACHABLE (website not connected), CONFLICT (another backup or a restoration is running on that website) and PERMISSION_DENIED (a backup your token cannot reach).
Body
backups(array of integers, required): ids of the backups to retry, 1 to 50, from “List backups” withfilter[phase][]=failed.
Errors
- 409: the storage quota is exhausted and no overage add-on is active. Nothing is retried.
- 422:
backupsis missing, empty, has more than 50 ids or contains an id that is not a backup.
Authentication
Personal access token created in the Modular DS dashboard; read-only tokens can only call GET endpoints.
Request
Response
202 Accepted - one copy re-queued, one skipped
