I have an AND gateway that is only executing one path. If I go into monitor the

Hi Joshua,

What it looks from the screenshot is that the lower path (that is executed) is executing faster than the upper path or vice versa. So, when either of the two paths reaches first to the terminate node, it is killing all the active nodes(since it is terminate node and not the end node) i.e the active 'AND gate'. In other words, the whole process is getting terminated , even before the second path from the AND gate begins to execute. Therefore killing the active AND gate node.

To check this, you can make the terminate node an end node and see what happens. I think both the paths from the AND gate will execute.

Further, to resolve this, you can place a COMPLEX gate before your sub-process node and route both the paths from the AND gate to this COMPLEX node, and configure the COMPLEX node in such a way that it should move ahead only when both the incoming flows have reached.

Do you get the same behavior if you remove the terminate?

Removing the terminate node works. Thank you.

It's still a good practice to have a terminate at the end of each process model. Work to address the logic in your node so that it functions with the terminate. You will likely need a complex node at the end of the model to collect your process flows.

Yes I managed a fix while keeping the terminate node.

If you are not using an AND gate to join multiple paths, but instead to separate multiple paths, then you should use a blank script task node instead. It would be worth it studying a little more on what gates are used for. In addition, its a good idea to label the script task as "split", and make sure your path flow lines are not over top of each other. When dragging a path flow, you can connect them to any 4 directions of the target node.