Looping: Always reverts to input from last item in the loop?

How exactly is the Loop Over Items node supposed to work?

I have a loop set up, which is being fed by a Split Out, and it runs as expected for the first item, but then once it gets to the end of the loop, it feeds the output of the last node into the Loop Over Items! That is, of course, not going to work…

I figured the “reset” feature would be what I needed, but the same behavior is observed even when setting “Reset”…

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

hello @oguruma

The loop node works very unpredictable :slight_smile:

Usually everything is fine, if every node in the loop chain outputs the same amount of items (e.g. 1 item at a time). But if not, then the Loop node start to grab that items and work with them, that is not what it should do (I suppose the issue is with the item linking that gets broken in that case).

As a general advice: Use sub workflows instead of the looping chain. That’s also better for the memory handling

The example of how to split the workflow into two. Main WF

Sub WF

PS I didn’t change the references, that lead to the Loop Node