Skip to main content

Delete Job

DELETE 
/jobs/:id

Soft-deletes a job and stops all its executions.

What Happens​

  1. Job state is set to "deleted"
  2. Evaluation is created to stop all active executions
  3. Job is excluded from default list views
  4. Job data is preserved for audit purposes (versions, history remain accessible)

When to Use​

  • Remove a job you no longer need
  • Clean up after testing or development
  • Decommission jobs for replaced services
  • Archive old jobs while preserving audit trail

State Validation​

By default, jobs can only be deleted if they are in a deletable state (stopped, completed, failed). Use force: true to bypass state validation and delete jobs in any state (including running).

Async Behavior​

The API returns immediately after marking the job as deleted. An evaluation is created to asynchronously stop all executions. Monitor the evaluation to track cleanup progress.

Common Scenarios​

  • Delete completed job: DELETE /jobs/my-job (no force needed)
  • Force delete running job: DELETE /jobs/my-job with {"force": true} in body
  • Delete with reason: DELETE /jobs/my-job with {"reason": "Replaced by v2"} in body

Viewing Deleted Jobs​

Deleted jobs are soft-deleted. To view: GET /jobs?states=deleted

Request​

Responses​

OK