Fail jobAdded in 8.6

POST 
/jobs/:jobKey/failure

Strongly Consistent About endpoint data consistency

Mark the job as failed.

Required permissions

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

Resource type	Permission
PROCESS_DEFINITION	UPDATE_PROCESS_INSTANCE

Request

Responses

204

The job is failed.

400

The provided data is not valid.

404

The job with the given jobKey is not found. It was completed by another worker, or the process instance itself was canceled.

409

The job with the given key is in the wrong state (i.e: not ACTIVATED or ACTIVATABLE). The job was failed by another worker with retries = 0, and the process is now in an incident state.

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 .