Purge a run now | CloudRaker documentation

Deletes a run’s files and outputs immediately, ahead of its TTL.

Anything still in flight is cancelled first. Idempotent: purging an already-purged run still answers 204.

To keep the results instead of destroying them, call POST /v1/runs/{id}/keep. To stop the work but leave the files until expiry, use POST /v1/runs/{id}/cancel.

Deletes a run's files and outputs immediately, ahead of its TTL. Anything still in flight is cancelled first. Idempotent: purging an already-purged run still answers `204`. To keep the results instead of destroying them, call [POST /v1/runs/{id}/keep](https://docs.cloudraker.com/api/cloud-raker-api/runs/keep-run). To stop the work but leave the files until expiry, use [POST /v1/runs/{id}/cancel](https://docs.cloudraker.com/api/cloud-raker-api/runs/cancel-run).

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

idstringRequired>=1 character

Response

Purged.

Errors

404

Not Found Error

429

Too Many Requests Error