Cancel a running ingestion job early
Ask an active job to stop. Cancellation is cooperative: a running job stops between documents, and what it already ingested stays rather than being rolled back.
POST
Cancellation is cooperative. A job that is
pending or queued never starts. A running job stops between documents, and documents ingested before it stops remain in the collection. The job’s status becomes cancelled once it has stopped, so poll Get a job to confirm. A cancellation applies to the current attempt only: if that attempt ends before it next checks, the job keeps the status it ended with, and if it failed and is retried, the retry runs.
requested is false when there is no active job with this ID in your organization. That covers a job that has already ended, an ID that does not exist, and another organization’s job, which are deliberately not distinguished. Only an ID longer than 64 characters returns 404.
Cancelling requires a role that can add documents. A read-only member receives 403.
string
required
Job ID (a UUID).
Response
boolean
required
true when cancellation was recorded on an active job. false otherwise.Last modified on September 26, 2026