Resolve incident
POST/incidents/:incidentKey/resolution
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.
Request
Responses
- 204
- 400
- 404
- 500
- 503
The incident is marked as resolved.
The provided data is not valid.
The incident with the incidentKey is not found.
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. 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 .