Unexpected Node

[samlaw168]

Current Behavior

"↵↵Unexpected Node Error↵↵Info:↵ Node object is not a node-red Node↵Stack:↵ TypeError: Cannot read properties of undefined (reading 'length')↵ at nodeInstance.Node.close (/opt/node_modules/@node-red/runtime/lib/nodes/Node.js:319:41)↵ at stopNode (/opt/node_modules/@node-red/runtime/lib/flows/Flow.js:757:31)↵ at Flow.stop (/opt/node_modules/@node-red/runtime/lib/flows/Flow.js:388:35)↵ at /opt/node_modules/@node-red/runtime/lib/flows/index.js:481:43↵ at Array.forEach ()↵ at stop (/opt/node_modules/@node-red/runtime/lib/flows/index.js:477:19)↵ at /opt/node_modules/@node-red/runtime/lib/flows/index.js:220:20↵↵Please report this issue, including the information logged above:↵https://github.com/node-red/node-red/issues/↵********************************************************************"

Expected Behavior

No response

Steps To Reproduce

No response

Example flow

paste your flow here

Environment

• Node-RED version:
• Node.js version:
• npm version:
• Platform/OS:
• Browser:

[hardillb]

@samlaw168 we are going to need some more context here for this to be useful.

Please fill out the complete template, especially the versions and what you were doing or had changed before the error was raised.

[knolleary]

The particular info that would be most helpful is what extra nodes you have installed. This error is being caused by one of those nodes and should be raised against it. The reason the log asks you to report it here is that it can be tricky to identify which node caused it. Once we have figured that out, we can redirect the issue to the right place.