When the purge last ran, and whether that is recent enough
const url = 'https://beta-api.plune.ai/v1/admin/purge';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/admin/purge \ --header 'Authorization: Bearer <token>'For the schedule to read back after sweeping, not for a screen. stale is true when the last sweep is over 48 hours old OR none has ever run — a deployment that has never purged is exactly the state worth an alarm.
Authorizations
Section titled “Authorizations ”Responses
Section titled “ Responses ”The last sweep
object
The queue of objects to delete from customers’ buckets (#948). Absent only if the count itself could not be read.
object
Objects waiting for their deletion.
Of those, the ones whose last attempt failed or was refused.
Of those, the ones that have failed for 7 days. They were written to the log once and stay in the queue, retried daily.
When the oldest waiting object was queued.
Of the failing ones, how many per reason of the last failure: other_bucket, outside_folder, status_<http code> (the bucket answered with it), network, timeout, tls, unresolvable, internal_address, not_https, ip_literal, redirect, error. Only these fixed words, never a key, a link or a bucket name; empty when nothing is failing.
object
Example generated
{ "lastPurgeAt": "2026-04-15T12:00:00Z", "stale": true, "storageDeletions": { "queued": 1, "failing": 1, "stuck": 1, "oldestAt": "2026-04-15T12:00:00Z", "byReason": { "additionalProperty": 1 } }}No / invalid token or session
The caller does not own the application
object
Example generated
{ "error": "example"}