ERROR: Cannot read properties of undefined (reading 'name')

[krthkntrjn]

This seems to be similar to the problem I have posted on Mistral Cloud Chat Model Node, where I get the error “Cannot read properties of null (reading ‘length’)”.

This was working perfectly fine 2 days ago, suddenly started giving this error yesterday morning.

[krthkntrjn]

The Cannot read properties error automatically went away when we upgraded to latest 1.38 version. You may want to try that.

[OhNo]

I just started having this issue today as well. Seems random as I changed a description in a n8n Workflow Tool and then I started getting:

“Cannot read properties of undefined (reading ‘name’)”.

My Setup:

• n8n version: 1.54.4
• Database: (Default SQLite)
• Running n8n via: Docker, cloud
• OS: Ubuntu 22.04

[Jon]

@OhNo can you open a new topic and complete the template, the error is very generic and it is likely different causes. If you can share the workflow that triggers the issue we will be able to find out what causes it

[netroy]

please check this previous comment:

ERROR: Cannot read properties of undefined (reading 'name')

Cannot read properties of undefined is a generic error, and it’s likely that this is caused by some other part of the code. To be able to fix this we’d need the full stack-trace. If you want, I can send you a Sentry key, that you can set on your deployment, and when this error happens next, we’ll have the stack trace and we can then easily fix this. Let me know if you are willing (and have access) to set an additional env variable on your n8n deployment. I can send the key over in a direct mes…

[OhNo]

@netroy How do I provide a full stack trace?

[dimitrihartt]

I have been having the same issue here! And what I can “sense” is that it has to do with the redis addon, it looks like it has to do with the type that stores the variable that comes from redis. The default output of redis is text (string) and it needs to be treated like that.

In my case I have redis to store a false/true value and when it comes to get that value I need to use: “propertyName?.toBoolean” when trying to receive the value from getRedis.

That seems to solve the problem. It means it has to do with around that.

[donniedarkowindsalt]

@donniedarkowindsalt

ERROR: Cannot read properties of undefined (reading ‘name’)

Now I’m seeing an error ERROR: Cannot read properties of null (reading 'name')

at least it’s not undefined anymore

[jxyz]

I had this problem with the stop and error node - I did not enter an error message. I works in dev mode, but fails when triggered by another workflow. It even shows an red indicator, but it looked like the default design to me

[netroy]

If any of you are seeing this issue on your cloud instance, please send me a DM mentioning this thread, and with your cloud instance name/url.
Then we can try to get the relevant stack trace, and get this fixed.
Trying to fix this without a proper stacktrace is like trying to find a needle in a barn.