In my Add Category node I’m getting the error:
Cannot read properties of undefined (reading ‘name’)
Since version 1.75.2.
I must admit that I do not understand why this is happing suddenly, is there anyone that can explain it to me why this isn’t working anymore in my Add Category node:
// Loop over input items and add categories
for (const item of items) {
item.json.categories = [$node["Loop Over Items"].json["tag"]];
}
return items;
Till today n8n was completely happy with getting the tag from “Loop Over Item” :S
Thanks for thinking with me
What is the error message (if any)?
Er ging iets mis met...
Workflow
NOS
Error
Cannot read properties of undefined (reading 'name')
Last node executed
Add category
Execution URL
https://n8n.golgi.nl/workflow/rXGnabaYnNXEW74N/executions/25425
Stacktrace
TypeError: Cannot read properties of undefined (reading 'name') at standardizeOutputRecursive (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Code/utils.js:25:35) at standardizeOutput (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Code/utils.js:31:5) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Code/Code.node.js:142:47) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:632:19) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:890:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1224:20
Hi - I started to get this exact same error on a code node of mine today only after upgrading to 1.75.2 (I was on 1.74.1 before).
To make things more odd, the workflow and code node that are having problems sometimes work fine when run in test mode (even using the exact state from a failed execution via “Debug in editor”, and I got it to succeed in some cases by renaming the title of the code node.
I haven’t noticed any other workflows failing in the same way.
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on ARM64 AWS EC2
Operating system: Ubuntu Linux 22.04.5 LTS / Docker Engine 27.5.1
Here’s the code node that is failing, and the node before it with some pinned sample data. The code node is just sorting a dictionary by the value of a key in each object.
Sentry is configured for my system with a DSN given to me by @netroy
I have the same issue on version 1.75.2 - When i restart the failed executions, the named error is gone. I hope that the next version is fixing it. Thanks.
Thanks. I’ve deployed a 1.76.1 image to test. The workflow in question for me is one that only gets hit a few times a day, so I’ll report back once I have some data.
I have updated my instance to the pre-release version 1.75.2 and since then the error has also disappeared. Positive feedback from me too. Thank you very much!
