I had a process model which gets information from third party through integration.
It ran specific nodes for 785 etc times with no traces and paused by exception.
All the active nodes in Green ran 700times and Paused by exception.
How to debug this issue.
Discussion posts and replies are publicly visible
Can we see the rest of the model?
What's obscured by the spawned nodes window?
sure,
How many times did Routing Decision run? When seeing similar to this in my own project, it was an issue with subprocess not terminating the way one would expect, causing multiple outflows. Meaning, it's likely you somehow have 785 instances of the line between Routing Decision and Case Status, or 785 outputs of Case Status.
Looking very closely at this picture, I think you have arrows going in both directions between "Requires S24 Review" and "Determine if Failed" (though it is very hard to tell / confirm). It could be bouncing infinitely back and forth...
Please check the connectivity between the green colored nodes.
I see the same thing you're seeing, Steven, and all sorts of other strange paths the connections are taking. Whenever you have multiple outputs of a process node, they all run. When multiple inputs go into a script task, the script task is run once for each time process flow reaches it.
So it looks like you are going back to the first script task and starting the whole thing over again repeatedly until you finally terminate the process.
As others have suggested you should delete all connections between these nodes and rebuild them from scratch. Leave the nodes where they are and reconnect them.