cleanup_start
Start a background cleanup of resolved requests (never pending ones or files they reference). It runs in small batches, so requests and decisions keep working. Local, and decide scope on paired devices.
Request Body required
Section titled “Request Bodyrequired”Which resolved requests a cleanup covers (POST /v1/storage/cleanup body,
GET /v1/storage/estimate query). Both limits apply together.
object
What a cleanup removes.
Only requests resolved at least this many days ago; 0 = every resolved request.
Keep the newest this many resolved requests (requests resolved in the same millisecond as the last one kept stay too); 0 = no count limit.
Responses
Section titled “Responses”Started; poll GET /v1/storage/cleanup/{id}
A background cleanup. The daemon runs one at a time in small batches, so requests and decisions keep working while it runs.
object
What a cleanup removes.
0 = every resolved request.
Newest resolved requests kept; 0 = no count limit.
Items to process, counted at the start: requests (history) or files (files).
Items processed so far.
Bytes freed: removed files plus database pages released by deleted rows.
Returning freed database pages to the filesystem (incremental vacuum).
Unix milliseconds.
Set when state is failed.
Remote device without decide scope
A cleanup is already running; job is that cleanup