I am trying to move to the next item in the loop node if true but it still loops over every object and then does not move on to the next row. I am not sure where I am going wrong.
@spencerbf , without diving into the complexity of the workflow and just checking the interconnections of the nodes (it is just a rational guess!) I believe that there is a missing link from the inner (nested) loop back to the parent (outer) loop.
The point is, the loop has to be complete, no loose ends within the loop. Any data flow has to end at the beginning of the loop eventually.
Technically speaking, having a nested loop does not necessarily “break” (prevent iterating) the parent loop. It’s just the outcome appears to be not what one might expect. I created a test workflow to check out the outcome of having the nested loop and here what I got.
Thus, while it is still possible to utilize a nested loop the result of it is not likely what one would expect. It is a good suggestion to stay out of nested loops .
Now, whether it’s recommended or not is an important point of consideration:
As seen here, 5 starting items can lead to a total of 125 iterations, in such a wf, and that could rapidly lead to a huge spike in memory usage and possibly app crash.
Also, as suggested above, you need to make sure that the loops are properly closed off. (Advice: Always exit a loop using the Loop node’s Done property)
.