in the attached process I have a service task linked to a timer boundary event of my user task (e.g. a reminder).
The user task is performed using the rest APIs:
Where the localVariable set is OUTCOME=“exit”.
In the service task I’m using a JavaDelegate which sets a local variable with the same key OUTCOME=“done”
In the outgoing flows from the exclusive gateway I have expressions that check the value of the variable OUTCOME
When the user task and the the timer event are created Camunda creates a new execution for the user task and uses the process instance execution for the timer.
When the conditions are evaluated Camunda obviously is reading the execution to which the sequence flow is attached (the process instance) and is finding OUTCOME=“done”.
In my opinion the user task shouldnt be moved to a child execution but must stay on the process instance execution.
If I remove the timer (and also when I have forks with parallel executions) everything works as intended.
MarcoProcessTest.bpmn (6.4 KB)