Split out - This node runs only for first item

[jbo-tech]

Hi everyone,

I’m currently facing an issue with the Split Out node in my n8n workflow and I’m hoping someone can help me out.

Problem Description: I have a Split Out node that is supposed to process 100 items. While all 100 items are correctly identified and seem to be processed, only the first iteration appears to be executed. The output I receive is only for the first item, and the rest are not processed as expected.

I have unchecked the “Execute Once” option.

Actual Behavior: Only the first item is processed, and the output is limited to the first iteration.

Additional Information:

• n8n version: 1.91.2
• Self-hosted with docker

Screenshots:

I think i miss something how the split out node works.

Has anyone else encountered this issue or have any suggestions on how to resolve it? Any help would be greatly appreciated!

Thank you in advance.
jbo

[mohamed3nan]

Hi @jbo-tech Welcome to n8n community

---

What do the 100 items look like?

I believe they might not be valid inputs for the NocoDB node, which could explain why there is no output.

Please share screenshots of the split-out output and confirm that all inputs are valid for processing by the NocoDB node.

[Wouter_Nigrini]

Please share youre workflow in a code block

[jbo-tech]

Hello,

Thank you for your quick answer.

@Wouter_Nigrini
Here is the workflow.
I just add some code block to try to understand what is happening:

@mohamed3nan
Here is the data :

After the nocodb node :

---

Does this can help?

The more i think about it the more i think it is due to the “get many” nocodb node. And the “Loop Over Items” node should solve the issue.

Thank you in advance for the help.

[mohamed3nan]

Hi @jbo-tech,

Thanks for the detailed explanation!

@jbo-tech

The more i think about it the more i think it is due to the “get many” nocodb node

Yes, you’re correct, I think so too.
Try validating this by changing the Limit to just “1” instead of “50” If it returns all items, then that is correct, but of course, you wouldn’t want only one, so:

@jbo-tech

And the “Loop Over Items” node should solve the issue.

You’re right again, “loop over items” should solve the issue, However, there’s a trick here: the output will be the total items multiplied by items output from the NocoDB node, If that’s what you’re looking for, great!

If you want the items from the NocoDB node to be nested under their respective item, you might need to implement some merging logic…

[Wouter_Nigrini]

I think since you’re effectively trying to look up multiple records and n8n uses loops internally by default, you can change your nocodb node to just Get and not Get Many. This will basically get each item from the list of 100 and then return a list of 100 items it found in the db.

i generally only use the loop node when i need to do specific manipulation for each item on my list, where as with your flow, it looks like you’re just trying to get back 100 items from an id.

[jpteixeira99]

I’m currently running into the same issue. At first I thought that it was because when testing it was only executing the first item but it also happens in production. What’s interesting is if you place an aggregate node after split out it does aggregate all input items correctly, meaning that they are indeed being returned by the split out node in some form, just not being run through the subsequent nodes. I will use the “Split In Batches” node for now.