Delete a job

When to call it

Scheduled cleanup normally removes a job and its stored result between fifteen and thirty minutes after the job's last change when a successful run reaches that job within its per-run capacity. Two missed four-minute sweep runs fit within thirty minutes, including execution, only if the next run succeeds and reaches the job. Further failed runs or a backlog beyond that run's capacity can delay removal beyond thirty minutes and require later successful runs. This endpoint is for the case where waiting is not good enough: you have read the result, written it to your own store, and want the copy here gone now.

It deletes the job record and the payload together. The response is a plain acknowledgement; there is nothing to read afterwards, and a second delete answers 404.

Calling it is optional. Without that call, scheduled cleanup normally removes the job between fifteen and thirty minutes after its last change when a successful run reaches that job within its per-run capacity. Two missed four-minute sweep runs fit within thirty minutes, including execution, only if the next run succeeds and reaches the job. Further failed runs or a backlog beyond that run's capacity can delay removal beyond thirty minutes and require later successful runs.

Request

Errors

A job still running cannot be deleted. QUEUED and IN_PROGRESS answer 409 CONFLICT; wait for COMPLETED or FAILED and try again. There is no cancel operation — this endpoint does not stop work in flight, and a run already spent is not refunded by deleting the job it paid for.

A job your credential did not start answers 403: another organisation's job, one another API client of yours started, or one a person started in the web application or the API tester. One that never existed — or has already been swept — answers 404.