# Very weird/unexpected signals from flow

**URL:** <https://discourse.nodered.org/t/very-weird-unexpected-signals-from-flow/34733>\
**Category:** General\
**Created:** [24 October 2020 04:34 UTC](https://discourse.nodered.org/t/very-weird-unexpected-signals-from-flow/34733 "2020-10-24T04:34:45Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 October 2020 08:58 UTC](https://discourse.nodered.org/t/very-weird-unexpected-signals-from-flow/34733/6 "2020-10-24T08:58:46Z")

</div>

> [@Trying\_to\_learn](#):
>
> when I get signals at 15:00 I am confused.

Possibly this problem. Caused by node red starting up before the system clock is initialised (possibly due to slow wifi startup or similar). There doesn't seem to be a solution so far.

> [@Inject node runs late sometimes](https://discourse.nodered.org/t/inject-node-runs-late-sometimes/30365/):
>
> Hi folks, I have set up the Inject node to trigger an audible reminder using Google Home at 3.55pm on a Tuesday. But sometimes (not every day) it happens a random time later, say 4.10pm! I am running Node Red on a Raspberry Pi, native not in a Docker container. Here is some simplified code that triggers at 4pm to reproduce the problem easily: [{"id":"d3d44654.2e41c8","type":"inject","z":"f72ea602.fbc808","name":"@4pm every day","topic":"","payload":"","payloadType":"date","repeat":"","cronta…

---

_[View the full topic](https://discourse.nodered.org/t/very-weird-unexpected-signals-from-flow/34733)._