Above image is the result of querying the index - operate-incident-8.3.1_
Hi @Sathiarekha
Pending state means that the incident is not resolved yet
Regards,
Alex
To resolve a PENDING incident in Camunda 8 using the Java client, you typically retry the failed job associated with the incident. Camunda 8 incidents are usually linked to a job failure (e.g., a service task with a worker that failed).
Common Lifecycle States of a Camunda 8 Incident:
| State | Meaning |
|---|---|
| PENDING | Incident created but not resolved or acknowledged yet. |
| RESOLVED | The underlying issue has been fixed, and the incident was cleared (automatically or manually). |
| DELETED | The incident was removed (typically via API or internal logic) — may happen if the process instance is deleted. |
Based on our observations, only incidents that are in ACTIVE state can be resolved. When there is an incident in PENDING state, the incident is not shown up in the Operate UI and it indefinitely stays in progress state. So there is no way for me to resolve it in from the Operate.
Images for reference:
It seems the screenshot from the initial description correlates with another instance.
only incidents that are in ACTIVE state
The ACTIVE states refer to the instance state, not to the incident state on that screenshot.
This is how the incident looks in Operate(it’s red):
The green color means that a token is on that service task at the moment.
JFYI from the docs:
