Loop Nodes failing (routing to 'Done' branch) when receiving multiple execution waves

[Parintele_Damaskin]

Hey @PBI_RS !

Have you tried “Reset” option in the 2nd Loop?(with an expression relative to the last node runned before the 2nd Loop).. eg :

{{ $prevNode.name === ‘SetJson’ }}

Try maybe as well a sub-workflow for that part,(this is how n8n recommends?) avoiding loops inline that needs downstream precessing and consumption of resources may be hight.

Cheers!

P.S found this relevant topic from a respected community staff member:

Loop Node Only Processes the First Item - How to Fix?

Hey @Gustavo_Borges, I have just picked this one up, The loop node can be tricky at times. So in this case the reset option needs to be used to tell the Loop node that it is a new set of data but as you probably noticed while testing if you just enable reset it will run forever as it will reset for every item that comes in from the loop branch. This brings the new question… How do I reset it for the second run of items? The example workflow that @ihortom gave us is below, In this workflow we w…