Loop pagination: how to keep feeding new items into a loop without Split In Batches staying ‘Done’?

[hassan_A]

Hi all,

Goal (single execution):

Run a search → get a list of URLs (e.g., 50).

Process them 10 at a time until the page is 100% done.

Only then fetch the next page of results (URLs 51–100), and repeat.

Keep going until no more results (or a stop rule).

Problem:

Once Split In Batches finishes, it stays Done.

If I try to “refill” it with new items, the flow keeps following the Done branch instead of looping again on the new page.

I don’t want to rely on “Reset” on Split In Batches.

Hard requirement:

The next page must start only after the current page’s items are completely processed (i.e., URL 51 must not start before URL 1–50 are done).

One run only (no separate executions).

What I’m looking for:

The recommended pattern to achieve this in n8n without using Split In Batches reset.

I’ve seen people suggest a while-loop using MERGE (Append) as a loop gate for pagination, or moving the batch work to a sub-workflow.

What’s the cleanest, stable wiring for: “finish page → then fetch next page → then process 10-by-10 again,” all within one execution?

Thanks a lot!

[moosa]

hey @hassan_A hope you are doing well.
here is an example:

what it does in code node is generate 2 batches of 5 urls(10 total) and runs them after all urls are run then generate 10(5-5) and runs similar to your case.