i use camunda zeebe engine 8 and face a random issue it wasn’t happened before
as i have a running instance when i sent back for previous node i got duplicated threads (2 threads inside the node i returned back ) i use inclusive gateway
any one can assist on this
Hi @khalidnouh
Could you please share your model?
From the screenshot, I see a lot of crossing lines which makes the model unreadable and definitely can lead to elements being activated multiple times.
Hi @khalidnouh
Since we can’t move any of the lines around on the screenshot, we can’t really trace it.
What HassanG was asking for was the .bpmn file to be uploaded (we don’t need the actual connectors that run the script tasks)
From what I can see, it looks like:
Initial Task always flows to “Next Approval Step (1)” and then it flows into an Inclusive Split.
The Inclusive split seems to have 2 paths out: “If Rejected” and “If Approved”. I would recommend replacing any Inclusive Split that has binary options like this with an Exclusive split. That will make sure that there is always only one path selected out of it.
As HassanG noted, if we have the actual BPMN file (rather than screenshots), we can likely get to the bottom of this with you.