Retry Cleanups
POST/api/v1/admin/cleanups/retry
The lossless counterpart of /name-fences/release: instead of freeing the name and abandoning the physical residue, this re-runs the cleanup so the reservation is released on the normal all-steps-succeeded path. Targets any non-completed checkpoint — including exhausted (re-arms the reclaim series at attempt 1) and the pre-reclaim backlog the scheduled pass skips as too old. A running checkpoint younger than an hour is refused (a live run may hold it); an older one is a dead mid-run worker, and re-dispatching it is safe because every step is an idempotent DROP.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 405
- 409
- 410
- 413
- 415
- 422
- 429
- 500
- 502
- 503
- 504
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Conflict
Gone
Request Entity Too Large
Unsupported Media Type
Unprocessable Entity
Too Many Requests
Internal Server Error
Bad Gateway
Service Unavailable
Gateway Timeout