Skip to main content
Stop a bulk job that hasn’t finished. Items not yet started are cancelled; items already running are allowed to finish.
cancelBulkOperation stops a job you submitted. It is best-effort and irreversible: items still QUEUED are cancelled, while items already RUNNING are allowed to finish and record their results. It does not roll back work that has already completed.
Available in staging only at this point.

Requirements

  • Authorization: Basic <API_KEY>
  • The bulk API capability on your application.
  • The job must belong to your application — an unknown or other-app job id returns not-found.

Mutation

Response

Arguments

Response fields

Errors

Cancelling an already-finished or already-cancelled job is not an error — it returns the job unchanged (see below).
Cancel is idempotent and safe to retry. Calling it on a job that is already finished (COMPLETED, COMPLETED_WITH_ERRORS, FAILED) or already CANCELLED returns the job unchanged — it never errors and never reverses completed items. Because in-flight items are allowed to finish, poll the job with Track a Bulk Job if you need the settled counts after cancelling.