the IF checks if entry is Master or not, IF it’s master executes the two API at the top, if it’s not a master skips those two API
Then I have a Set node that “recaps all the data” to make it easier to access the data in the next nodes. But when the two API at the top don’t execute I get this error:
An expression references the node ‘xxxxx’, but it hasn’t been executed yet. Either change the expression, or re-wire your workflow to make sure that node executes first.
Looking at your expression syntax you are using the older $item("0").$node["nodename"] which has been replaced with $('nodename').first() I would start by updating all of your expressions.
The next thing to check is has the node the expression is calling been executed and has an output? If the node doesn’t run you won’t be able to reference it, This was something that changed with the launch of v1 so I wonder if maybe you were using a very old version and recently updated.
We did add $("<node-name>").isExecuted recently which you can use to determine if a node has executed before trying to use the value which could help you in this case.
I get the expression syntax using the n8n in-built method:
(Which seems, per your comment, it gives old syntax)
What happens if I don’t update the expressions? I have about 100 workflows with a lot of steps in each one that uses the expression from the above screenshot…
As explained in the post @Jon the node didn’t execute because the IF determined the current entry is not a master so the two API at the top didn’t run (which is what’s grey in the second screenshot).
PS: I’m running almost the latest version, and this is a fresh new instance created 3 months ago…
PS2: Can’t you guys add in a future update something that auto-converts automatically ALL the old expression to the new one for us? I mean If I have to change each expression it could take a year
I will get a ticket raised about the old expression style being used. We shouldn’t need to auto convert all the old options as they should still in theory work which I suspect they are here but the issue will be that the node never runs which comes down to workflow design.
