Multiple executions due to results from previous node

In a several workflows I have observed that some nodes are getting executed multiple times if the previous node has more than one result. In excerpt of a workflow below this happens on the second node for example four times if the result of the first node was to set four tags.

I already found out that I could prevent this by adding an item lists node and set it to “limit”, but is this really necessary and why it multiples the following execution even when there is no dependency between the two nodes?

Information on your n8n setup

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

you can set the “execute once” setting.

1 Like

Can’t be easier :man_facepalming: - thank you @mellesc :slight_smile:

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