Retrieving a parallel node no longer works

Describe the problem/error/question

Hello,

I have a workflow that I created on June 2023 and that was working fine until then, but that stopped working after a recent update. Well, there are three workflows affected by the same problem, but I’ll take this one as an example.
In this workflow, I retrieve emails and loop over them to apply the filters I have in my database. In order to avoid retrieving the filters from the database on each loop, I had made a branch parallel to the loop which retrieved them only once, and I managed to retrieve these nodes running in parallel in the loop, like this:

Except that since a recent update, it no longer works:

With this error:

Error finding the referenced node [line 3]

ExpressionError

Line 3 being:
const filters = $(‘Filters’).all()[0].json;

The last time it worked was on June 5. Since then, all my automations that have the same type of operation have broken down.
If I put the nodes in the loop, it works, but they are called as many times as there are loops, and in some of my workflows this can be as many as 200 times…

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.106.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Unraid

Yep same issue here, I did read some conversations about it before. Not sure what the conclusion of it was though. I think it is being fixed in an upcoming version :slight_smile:

1 Like

What if we use merge node?
And it’s look like the OP workflow already too “old”, is that can be the problem?

It can be fixed with merging the branches yes, but it breaking all kinds of flows as the thing changes is a big issue.

I guess that’s the perfect fit solution since n8n will be always updating (?)

Not saying using merge nodes to combine branches(wait for branches to finish) isn’t a good idea. I normally do that personally. But there is loads of flows out there that do not and then this is a breaking change. :slight_smile:

1 Like

Ahhh. I see, thanks for the explanation mate!

1 Like

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