# Help with messages seen at start up

**URL:** <https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497>\
**Category:** General\
**Created:** [8 June 2025 23:05 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497 "2025-06-08T23:05:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [8 June 2025 23:05 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/1 "2025-06-08T23:05:33Z")

</div>

I'm seeing this when I start NR on a remote machine.

GIVEN:  
I have now removed the `world map` node.

```auto
9 Jun 08:27:27 - [info] Stopping flows
9 Jun 08:27:27 - [info] Stopped flows
9 Jun 08:27:27 - [info] Updated flows
9 Jun 08:27:33 - [info] Starting flows
9 Jun 08:27:41 - [warn] Unknown context store 'memory' specified. Using default store.
TypeError: Cannot read properties of undefined (reading 'id')
    at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Subflow.js:209:140
    at Array.map (<anonymous>)
    at /usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Subflow.js:209:95
    at Array.map (<anonymous>)
    at Subflow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Subflow.js:209:62)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:224:41)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:394:33)
9 Jun 08:27:48 - [info] [worldmap:f83930ff.b21488] started at /worldmap
9 Jun 08:27:48 - [info] Started flows
9 Jun 08:27:53 - [error] [function:new delayed message send *] SyntaxError: Unexpected token '**' (body:line 12)
(node:17981) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
9 Jun 08:27:56 - [warn] [function:e5b70640.b5deb8] Name of the flow UPLINK monitor
9 Jun 08:27:56 - [warn] [function:e5b70640.b5deb8] Control signal received GO
9 Jun 08:27:56 - [warn] [function:adb6a8f1.5b1cf] Name of the flow History
9 Jun 08:27:56 - [warn] [function:adb6a8f1.5b1cf] Control signal received GO
9 Jun 08:27:56 - [warn] [function:6b5fb94d.48cbb] Name of the flow Machine_Health
9 Jun 08:27:56 - [warn] [function:6b5fb94d.48cbb] Control signal received GO
9 Jun 08:27:56 - [warn] [function:6d2db6bf.02be08] Name of the flow FTP
9 Jun 08:27:56 - [warn] [function:6d2db6bf.02be08] Control signal received GO
9 Jun 08:27:56 - [warn] [function:f76baf91.b55c7] Name of the flow Logging
9 Jun 08:27:56 - [warn] [function:f76baf91.b55c7] Control signal received GO
9 Jun 08:27:56 - [warn] [function:e20ff8a8.b2f2b] Name of the flow Events
9 Jun 08:27:56 - [warn] [function:e20ff8a8.b2f2b] Control signal received GO
9 Jun 08:27:56 - [warn] [function:6a013979.4c1ba] Name of the flow HDMI_CTL
9 Jun 08:27:56 - [warn] [function:6a013979.4c1ba] Control signal received GO
9 Jun 08:27:56 - [warn] [function:42ab6527.a31694] Name of the flow Schedule
9 Jun 08:27:56 - [warn] [function:42ab6527.a31694] Control signal received GO
9 Jun 08:27:56 - [warn] [function:7499c4.f53c6e3c] Name of the flow RealWorldControl
9 Jun 08:27:56 - [warn] [function:7499c4.f53c6e3c] Control signal received GO
9 Jun 08:27:56 - [warn] [function:0cd013885a2c0229] Name of the flow PlantWateringControl
9 Jun 08:27:56 - [warn] [function:0cd013885a2c0229] Control signal received GO
9 Jun 08:27:56 - [warn] [function:799b83aef439fca5] Name of the flow Tweaks
9 Jun 08:27:56 - [warn] [function:799b83aef439fca5] Control signal received GO
9 Jun 08:27:56 - [warn] [function:317a055b.f7513a] Name of the flow Door CTL
9 Jun 08:27:56 - [warn] [function:317a055b.f7513a] Control signal received GO
9 Jun 08:27:56 - [warn] [function:1e9bd9fd.fd2ea6] Name of the flow Weather
9 Jun 08:27:56 - [warn] [function:1e9bd9fd.fd2ea6] Control signal received GO
9 Jun 08:27:56 - [warn] [function:Eror notifier] Name of the flow WorldMap
9 Jun 08:27:56 - [warn] [function:Eror notifier] Control signal received GO
9 Jun 08:27:56 - [info] [mqtt-broker:TIMEPI MQTT] Connected to broker: mqtt://192.168.17.39:1883
9 Jun 08:27:57 - [red] Uncaught Exception:
9 Jun 08:27:57 - [error] TypeError: sendEvent.destination.node.receive is not a function
    at Immediate.<anonymous> (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:831:52)
    at processImmediate (node:internal/timers:466:21)

```

What gets me is the `[warn] Unknown context store 'memory' specified. Using default store. TypeError: Cannot read properties of undefined (reading 'id')`  
bit.

Not sure it is THAT urgent, as it is a WARN. But....

But the last bit is worrying.

How can I find out what's happening.

Ok, I haven't looked at the logs yet.

But this is what I know at this time.  
More specs coming as soon as I can get it running again.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [9 June 2025 00:17 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/2 "2025-06-09T00:17:44Z")

</div>

> [@Trying\_to\_learn](#):
>
> What gets me is the `[warn] Unknown context store 'memory' specified. Using default store. TypeError: Cannot read properties of undefined (reading 'id')`  
> bit.

Check context setup, in settings.js

```auto
contextStorage: {
        default: {
            module:"localfilesystem"
        },
		memory: {
            module: "memory"
		},
	},

```

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 00:22 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/3 "2025-06-09T00:22:40Z")

</div>

Thanks shall do.

FYI, I've just updated the machine to NR 4.x

Still getting error.

Am about to check `settings.js` file shortly.

Sorry it is a screenshot, but this is now spewing on the startup.  
(I only ran `node-red`)

Not directly at you, but those weird paths.....  
`/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:811:40`

Who/what are they?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 00:29 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/4 "2025-06-09T00:29:36Z")

</div>

From `settings.js` file:

(sorry, I messed up the copy/paste)

I put in your stuff.

The _existing_ was (I believe) the _default_.

Running and that seems to have stopped.

Thanks.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 00:34 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/5 "2025-06-09T00:34:40Z")

</div>

NR up and running and I am seeing a lot of error messages - like the ones in the screen shot I posted.

I can't `copy` them as the option isn't here.

Here is the short version copy/pasted from the terminal

```auto
9 Jun 10:27:50 - [warn] [function:Eror notifier] Name of the flow WorldMap
9 Jun 10:27:50 - [warn] [function:Eror notifier] Control signal received GO
9 Jun 10:27:50 - [error] Error delivering message to node:undefined [undefined]
9 Jun 10:27:50 - [error] TypeError: sendEvent.destination.node.receive is not a function
    at deliverMessageToDestination (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:811:40)
    at Immediate._onImmediate (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:827:21)
    at process.processImmediate (node:internal/timers:476:21)
9 Jun 10:27:51 - [error] Error delivering message to node:undefined [undefined]
9 Jun 10:27:51 - [error] TypeError: sendEvent.destination.node.receive is not a function
    at deliverMessageToDestination (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:811:40)
    at Immediate._onImmediate (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:827:21)
    at process.processImmediate (node:internal/timers:476:21)
9 Jun 10:27:51 - [warn] [function:function 24] Payload rgb,2,0,0,0
9 Jun 10:27:51 - [error] Error delivering message to node:undefined [undefined]
9 Jun 10:27:51 - [error] TypeError: sendEvent.destination.node.receive is not a function
    at deliverMessageToDestination (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:811:40)
    at Immediate._onImmediate (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:827:21)
    at process.processImmediate (node:internal/timers:476:21)

```

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 June 2025 01:03 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/6 "2025-06-09T01:03:04Z")

</div>

# HUGE UPDATE:

This is coming (partly) from a subflow.  
Not entirely.

But I just noticed it was happening on a _SPECIFIC_ (ok, not only one) tab.  
I moved to another tab and the messages stopped.  
_(debug for current flow/tab)_

So.... As that tab/flow was not doing anything at this time, I disabled it.  
Sure enough it stopped.

Ok. Good - kinda.

Then went to another _important_ tab.  
The messages - maybe not EXACTLY the same - came back.  
😕  
But I thought I would not worry too much at this point.

For more information, go to my other thread:  
[More developments!](https://discourse.nodered.org/t/problem-detected-when-migrating-subglows-between-machines/97495/1)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [7 September 2025 01:03 UTC](https://discourse.nodered.org/t/help-with-messages-seen-at-start-up/97497/7 "2025-09-07T01:03:26Z")

</div>

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