Resolve incidentAdded in 8.6

POST 
/incidents/:incidentKey/resolution

Strongly Consistent About endpoint data consistency

Marks the incident as resolved; most likely a call to Update job will be necessary to reset the job's retries, followed by this call.

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 incident is marked as resolved.

400

The provided data is not valid.

404

The incident with the incidentKey is not found.

409

The incident cannot be resolved due to an invalid state. For example, the associated job may have no retries left.

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 .