This is how I am trying to use Inclusive Gateway in my requirement.
In my process, had one human activity followed by two parallel human activities. Each parallel human activity attached with boundary signal event. These boundary signal events are further connected to Inclusive gateway and Inclusive gateway is connected to the first human activity. This modelling is purely related to my customer requirement. Enabled Cancel Activity - true on both the boundary signal events.
If the boundary signal event is triggered through rest signal api, active tasks of 2 parallel human activities should be cancelled, execution flow of two boundary signal event should be converged at Inclusive gateway and proceed to the first human activity, this should create only one task for the first human activity.
The problem here, Inclusive gateway is not converging the flow at it's gateway, this is leading to creation of two tasks for the first human activity because of two execution flows of boundary signal events.
