The Workflow Incidents tab in the settings lists technical errors that occur during the execution of a workflow. Because such incidents can block running workflows, they should be checked and resolved daily.
Typical causes
| Cause | Example |
|---|---|
| Missing variable | An expected variable is not set in the case |
| Unresolvable condition | A FEEL expression on a gateway can’t be evaluated |
| Error in a ServiceTask | The executed function reports back an error |
How to resolve an incident
-
Open the incident
Open the affected row in the tab. You see the workflow, the case, and the error message.
-
Read the cause
The message tells you what's wrong – for example a missing variable, an unresolvable condition, or an error in a ServiceTask.
-
Fix it – in the case or in the editor
If a value is missing, add it as a placeholder in the case. If it's due to the model (a condition, a missing default path), correct the process in the editor. The instance elements help with narrowing it down.
-
Retry & close
Retry has the engine repeat the failed step. If it goes through, close the incident with Resolve incident.
How to prevent incidents
- Always provide a default path on exclusive gateways, so an uncovered case doesn’t create an incident.
- Check values before calculations with
isNullOrEmpty(...)andisNumber(...). - For error-prone tasks (e.g. LLM requests), set a retry of 1–3 in the editor.