A process instance is stuck at an inclusive gateway

[saig0]

Describe the bug

I have the following process with an inclusive gateway that joins two paths:

Given:

• The task A is active
• The task B is active

When:

• The task A is completed
• The error boundary event of task B is triggered

Then:

• The process instance is stuck and waiting at the inclusive gateway

To Reproduce

1. Deploy the following process inclusive-gateway-stuck.bpmn
2. Complete the job A of the task A
3. Throw a BPMN error for job B of the task B
4. Verify that the process instance is active and the inclusive gateway is not activated/completed

Expected behavior

The process instance detects that there is no active path to the inclusive gateway and activates/completes it.

Log/Stacktrace

Environment:

• OS:
• Zeebe Version: 8.6.0-SNAPSHOT
• Configuration:

[lzgabel]

🤔 I verified it on C7 and found that C7 has the same behavior. It seems that we need to solve this problem through some kind of dynamic detection.

Deploy the following process inclusive-gateway-stuck_c7.bpmn

[saig0]

@lzgabel thank you for checking the Camunda 7 behavior. :+1:

It is an interesting case. A detection on every command could be too resource-intensive. Maybe, we could add a detection when a path of a flow scope is completed/terminated (ref).