Suspend Batch operationAdded in 8.8

POST 
/batch-operations/:batchOperationKey/suspension

Strongly Consistent About endpoint data consistency

Suspends a running batch operation. This is done asynchronously, the progress can be tracked using the batch operation status endpoint (/batch-operations/{batchOperationKey}).

Required permissions

When authorization is enabled, this endpoint requires the following permission. See resources and permissions to learn more.

Resource type	Permission
BATCH	UPDATE

Request

Responses

204

The batch operation pause request was created.

400

The provided data is not valid.

403

Forbidden. The request is not allowed.

404

Not found. The batch operation was not found.

500

An internal error occurred while processing the request.

503

The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains RESOURCE_EXHAUSTED. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .