# Node-Red notification.warnings.undefined error and node-red crashing

**URL:** <https://discourse.openiap.io/t/node-red-notification-warnings-undefined-error-and-node-red-crashing/3256>\
**Category:** OpenCore\
**Tags:** agent\
**Created:** [April 13, 2026, 4:34pm UTC](https://discourse.openiap.io/t/node-red-notification-warnings-undefined-error-and-node-red-crashing/3256 "2026-04-13T16:34:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![renierduvenhage](https://discourse.openiap.io/letter_avatar_proxy/v4/letter/r/5f8ce5/32.png) [@renierduvenhage](https://discourse.openiap.io/u/renierduvenhage)\
**Post date:** [April 13, 2026, 4:34pm UTC](https://discourse.openiap.io/t/node-red-notification-warnings-undefined-error-and-node-red-crashing/3256/1 "2026-04-13T16:34:37Z")

</div>

Hi @Allan_Zimmermann

I have a working noderedagent packaged published to my own OpenCore image running in Azure cloud.

When starting the package from OpenCore on the remote nodeagent, node-red runs on localhost with the following error (note that no flows are created where typically, in the past, flow 1 would’ve been created):

 ![image](https://discourse.openiap.io/uploads/default/original/2X/2/2b44ec2cb3b0df478cedaf1dba7016c3b4f5fd1c.png)

Then, as soon as I create a new flow, the node-red instance crashes and the following output is displayed in OpenCore on the nodeagent debug page:

 ![image](https://discourse.openiap.io/uploads/default/original/2X/1/15743cc81a26ef098a480e26a205de134624ca66.png)

I also noticed there is no flows file generated for the node-red instance.

The user that is running the nodeagent with the openiap-noderedagent package has admin rights in OpenCore.

Not sure what would be causing this error?

---

<div class="post-metadata">

**Author:** ![renierduvenhage](https://discourse.openiap.io/letter_avatar_proxy/v4/letter/r/5f8ce5/32.png) [@renierduvenhage](https://discourse.openiap.io/u/renierduvenhage)\
**Post date:** [April 13, 2026, 5:55pm UTC](https://discourse.openiap.io/t/node-red-notification-warnings-undefined-error-and-node-red-crashing/3256/2 "2026-04-13T17:55:57Z")

</div>

I found the solution.

Seems like my Node-Red version in the noderedagent package was to old for NodeJS v24.

Changed the Node-Red version to v4.1.8, published a new agent and then ran a new package via the nodeagent.

All issues resolved.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.openiap.io/uploads/default/original/2X/a/a1ca7b164ac9a826839704d9ac82c7b5e6bcf557.png) [@system](https://discourse.openiap.io/u/system)\
**Post date:** [April 16, 2026, 5:56pm UTC](https://discourse.openiap.io/t/node-red-notification-warnings-undefined-error-and-node-red-crashing/3256/3 "2026-04-16T17:56:46Z")

</div>

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