After passing the first service task the engine creates a virtual unlimited number of User Tasks, see workflow attached:
We use the latest CAMUNDA Engine out of the box (docker). All service tasks have been implemented using the camunda-external-task-client-js lib.
Me question is: how do we prevent the engine from creating more than one user task?
As far as there is no user task involved everything works fine.
Any help is appreciated,
Guidotravel-expense-report.bpmn (8.3 KB)
I’ll take a look at this - it seems that there is a rouge sequence flow starting from and going to the service task.
Looks like a weird bug in how the modeler created the sequence flows.
Try this:
travel-expense-report-1.bpmn (7.9 KB)
You solved my problem. Thanks!
May You share Your findings with us?
Did You / shall I file a bug report?
I’m going to talk to the modeler guys about it - but basically you had a sequence flow leaving the service task and then coming backing into it - you can see the shadow of it here:
Not sure how it happened - can you let me know what version of the modeler you’re using?
In general the Modeler tries to prevent such situations from ever happening.
As an example, the next version of the tool is going to ship with additional improvements that make loops event more explicit:
If you come across such issue and remember how you were able to model it, report it as an issue.
