Get incident by key (alpha)
GET/incidents/:incidentKey
Returns incident as JSON.
This endpoint is an alpha feature and not enabled on Camunda clusters out of the box. See the Camunda 8 REST API overview for further details.
Request
Path Parameters
The assigned key of the incident, which acts as a unique identifier for this incident.
Responses
- 200
- 400
- 404
- 500
The incident is successfully returned.
- application/json
- Schema
- Example (from schema)
Schema
The assigned key, which acts as a unique identifier for this incident.
The process definition key associated to this incident.
The bpmn process id associated to this incident.
The process instance key associated to this incident.
Possible values: [UNSPECIFIED
, UNKNOWN
, IO_MAPPING_ERROR
, JOB_NO_RETRIES
, CONDITION_ERROR
, EXTRACT_VALUE_ERROR
, CALLED_ELEMENT_ERROR
, UNHANDLED_ERROR_EVENT
, MESSAGE_SIZE_EXCEEDED
, CALLED_DECISION_ERROR
, DECISION_EVALUATION_ERROR
, FORM_NOT_FOUND
]
Incident error type with a defined set of values.
Error message which describes the error in more detail.
The flow node id associated to this incident.
The flow node instance key associated to this incident.
Date of incident creation.
Possible values: [ACTIVE
, MIGRATED
, RESOLVED
, PENDING
]
State of this incident with a defined set of values.
The job key, if exists, associated with this incident.
The path from process instance via flow node ids and flow node instance keys leading to this incident.
The tenant id of the incident.
{
"key": 0,
"processDefinitionKey": 0,
"processDefinitionId": "string",
"processInstanceKey": 0,
"errorType": "UNSPECIFIED",
"errorMessage": "string",
"flowNodeId": "string",
"flowNodeInstanceKey": 0,
"creationTime": "2024-10-02T22:01:21.469Z",
"state": "ACTIVE",
"jobKey": 0,
"treePath": "string",
"tenantId": "string"
}
The incident Get failed. More details are provided in the response body.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
The incident with the given key was not found. More details are provided in the response body.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}
An internal error occurred while processing the request.
- application/problem+json
- Schema
- Example (from schema)
Schema
Default value: about:blank
A URI identifying the problem type.
A summary of the problem type.
Possible values: >= 400
and <= 600
The HTTP status code for this problem.
An explanation of the problem in more detail.
A URI identifying the origin of the problem.
{
"type": "about:blank",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string"
}