Critical Bug was found with Split in Batches node

I think I found a critical bug with Split in Batches node.

Situation:

I was working with Data bases and Split in Batches node. If I use this node inside loop everything works fine. But I need to clear data before next loop so I turned Reset Option in Split in Batches node. And then my webpage got frozen and nothing helped except server rebooting.

My simplified workflow:

Also I’ve tried to expand RAM on my server from 4gb to 8gb but it didn’t help.

I need to know how to how to clear data in second Split in Batches node to get actual data and without server crashing?

Information on your n8n setup

  • n8n version: 0.228.2
  • Database: SQLite
  • n8n EXECUTIONS_PROCESS setting: main
  • Running n8n via: Docker Compose
  • Operating system: Ubuntu

You cannot use a split in batches node inside the loop of another split in batches node.

2 Likes

Thank you for help!

And why so?

Because every node is independent and doesnt know if it is running in a nested loop.

3 Likes

@Eventurum ongoing, related discussion:

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.