Describe the problem/error/question Hello guys, I’m trying to understand the behavior of the new Split In Batches node with nested loops. In my example workflow I’m using the n8n training node to get 2 items, split them into batches of 1 (outer loop), then get 5 more items and again split them into…

Hi @antitalent , this seems like an intentional change to me. Nested loops are often really hard to read, so the built-in “merging” of the new node version hopefully means you no longer nested loops and can simply build sequential workflows instead. You can still keep using the old node version thou…

Note: i did not use the Reset option in the Split in Batches 3 nodes, as i perceive that that is now handled internally in the new node. … Also, if i do set the value of Reset to {{ $node["Split In Batches 3"].context["noItemsLeft"] }}, it results in an infinite loop: [image]

Additionally to this, new node is using data from last node instead only from oryginally set data. Split batch gets 4 items, sending only 2 (i set batch size for 1), and letting out 6 items in total in done branch. I saw additionally that batch node is using data from last node in loop (in my case…

Hi @n8n_Team , could anyone kindly provide an update regarding this issue? Thanks

Perhaps @Jon could provide an update tomorrow when he’s back in, as it’s a bank holiday in most of Europe today? :+1:

Hey @shrey-42 , I still have a note to look into this in more detail I just need to find a bit of time. Looking at your workflow in the old version you would use the reset option which doesn’t seem to be working in the same way in the new version so it sounds like that is a bug that needs to be reso…

Thanks a lot for making us aware of the issue. Had a look and found the “issue”. Have a PR ready locally and will after a conversation internally open it on GitHub.

Got now merged and will be released with the next n8n version.

New version n8n@0.234.0 got released which includes the GitHub PR 6437 .

Just wanted to follow up. Does everything now work as expected for everybody?

Split In Batches Nested Loops - New vs. Old Nodes

Questions

jan June 16, 2023, 7:47am 21

OK, got now fixed by adding another key to the context, which is called “done”. It gets set to true after the node did output data from the “done” branch. That allows now an easy reset for this double loops.

The PR will be revied and merged soon:

Split in batches returns less items than expected

Topic		Replies	Views
Split in batches returns less items than expected Questions splitinbatches	7	626	July 20, 2023
N8n Loop Stopped at Split-In-Batches node on 2nd loop (mine is not working) Questions looping	1	1187	July 26, 2023
Split in Batches - only process the first batch and the second batch onwards goes to done Questions splitinbatches	1	540	August 9, 2023
Please help me Understand the Different in SplitInBatches vs Direct approach Questions data-transformation , workflow-building	5	566	September 13, 2022
Critical Bug was found with Split in Batches node Questions splitinbatches	4	635	May 27, 2023

Split In Batches Nested Loops - New vs. Old Nodes

Related topics