Fail jobAdded in 8.6
POST/jobs/:jobKey/failure
Strongly Consistent About endpoint data consistency
Mark the job as failed.
Request
Responses
- 204
- 400
- 404
- 409
- 500
- 503
The job is failed.
The provided data is not valid.
The job with the given jobKey is not found. It was completed by another worker, or the process instance itself was canceled.
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.
An internal error occurred while processing the request.
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 .