Hi,
I have a process model where a rule is processed in a script task running parallel to a user input task. At the second AND gate, there are two possible scenarios:
First API Call Path Reaches the AND Gate First: The API path reaches the AND gate before the user submits the task. This scenario works as expected, triggering the next chained User Input Task (UIT) in the process after the submission of first UIT.
User Submits the Task First: The user submits the task before the API path reaches the AND gate. In this case, the next UIT is not triggered as expected.
anyone knows what's the reason for this to happen ?note : the script task is not an actual API call but just an expression rule with some dummy dataThanks
Discussion posts and replies are publicly visible
Does your Process instance get stuck some where in 2nd scenario or just that activity chaining breaks down if that happens ? if activity chaining breaks down, I would say that is expected as there is a race condition between two nodes and is creating confusion for the process. try simplifying the flow without the and gateway to avoid unexpected behaviour.
(note this appears to be a duplicate post, we discussed the reasons and ways to avoid this in the other similar original post by this user)