BUG: Random failures due to unable to lookup result from previously executed nodes

Describe the problem/error/question

2 days we upgraded from 1.102.3 to 1.107.3 and then some executions started failing. After further investigation, it turns out we’re fetching the output from a previously executed node to use as input in a later node, and it is for some reason undefined.

What is the error message (if any)?

The error we are receiving is unrelevant since its the fetching of previous output that fails.

Share the output returned by the last node

Left is previous output.
Right is the value found when the node was executed.

Information on your n8n setup

  • n8n version: 1.107.3
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): k8s
  • Operating system:

Just tried to upgrade to latest and we got the same problem right away.

Unfortunately this time a non backward compatible change was made to the database (User.Role) so I was unable to rollback to 1.102.3 and I had no relevant backup of the database at hand.

Fortunately I found a workaround. The data I was trying to fetch from an earlier executed node I also had stored in customData. So I added a new code node before my failing node, which takes customData and exposes to the next node (the one that failed), and now it has the data it needs to keep going.

Now I am just hoping this is the only problem we will run into. But this bug is quite bad for something I consider core functionality.

Information on your n8n setup

  • n8n version: 1.110.1

  • Database (default: SQLite): postgres

  • n8n EXECUTIONS_PROCESS setting (default: own, main): default

  • Running n8n via (Docker, npm, n8n cloud, desktop app): k8s

  • Operating system:

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