While troubleshooting an apparent error just now, I noticed that all completed instances of a relatively simple process with an AND gateway had failed to execute both of its outgoing paths. The key factor here is that the process chains (unattended) all the way to a Terminate node, presumably because after the user submits their task in this subprocess, they're expected to chain into a followup task back at the parent level.
However I never realized this constraint was in place - that is, the process executes all possible chained paths (up to and including a terminate) before it will execute the other AND gateway outputs. This seems like a bug to me - but am I wrong? Has anyone else noticed this?
I was able to recreate the behavior with this very, very simplified example process, if anyone's having trouble picturing what I'm referring to:
Discussion posts and replies are publicly visible
I have seen this before, especially since you chained the one. It was prioritized and terminated before the other path started. This is why you can't terminate or you have to have them come back together before terminating. I believe it has always been this way, and dare I say, expected.
It may have always been this way without me noticing - so in that respect expected. But it took me by surprise (unsurprisingly, it was set up this way in the system i inherited, so of course it consumed some troubleshooting effort on my part, and since the model in question was slightly more complicated, it caught me off-guard more easily).