# Has something changed with the delay node?

**URL:** <https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221>\
**Category:** General\
**Tags:** delay\
**Created:** [12 September 2023 06:21 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221 "2023-09-12T06:21:58Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [12 September 2023 06:21 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/1 "2023-09-12T06:21:58Z")

</div>

Hello everyone, its been a while 😅

This finding is prior to 3.1 (i'm sure it is), but Mrs Davies keeps bringing it up, because of the effect its having with automation.

I have noticed the delay node **WILL** pass a message that has `msg.reset` if:

- Its set to rate limit
- There is no other message being held.

I believe this is behaviour that started maybe 1-2 versions ago?

See below for a demo.  
If this is expected (new behaviour or otherwise) then cool, but not sure if this was intended?

![Sep-12-2023 07-17-03](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/4/a479807d254b2bbe3160a9090567576a04e53c63.gif)

```auto
[{"id":"847f3a065f5f8cdd","type":"tab","label":"Flow 1","disabled":false,"info":"","env":[]},{"id":"b0f341d4815fa7ea","type":"debug","z":"847f3a065f5f8cdd","name":"debug 4","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":1115,"y":100,"wires":[]},{"id":"a4a9b730b905294c","type":"delay","z":"847f3a065f5f8cdd","name":"","pauseType":"rate","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"hour","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":true,"allowrate":false,"outputs":1,"x":910,"y":100,"wires":[["b0f341d4815fa7ea"]]},{"id":"351578f6dd252a3f","type":"inject","z":"847f3a065f5f8cdd","name":"reset","props":[{"p":"reset","v":"true","vt":"bool"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":680,"y":220,"wires":[["a4a9b730b905294c"]]},{"id":"c944b4bae18a02ea","type":"inject","z":"847f3a065f5f8cdd","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":680,"y":100,"wires":[["a4a9b730b905294c"]]}]

```

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [12 September 2023 06:35 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/2 "2023-09-12T06:35:12Z")

</div>

I just tried this on one of my old NR instances on a PiZero in my kitchen, running V1.1.3 and can confirm that msg.reset messages are not let through at all

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [12 September 2023 06:40 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/3 "2023-09-12T06:40:26Z")

</div>

So seems this is new behaviour.  
I'll wait for someone from the core team to chip in before I raise anything on Github (as i'm not sure if this is now expected)

---

<div class="post-metadata">

**Author:** ![PdeJ](https://avatars.discourse-cdn.com/v4/letter/p/c89c15/32.png) [@PdeJ](https://discourse.nodered.org/u/PdeJ)\
**Post date:** [12 September 2023 09:43 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/4 "2023-09-12T09:43:37Z")

</div>

Also can concur, msg.reset is not let through on a Pi2B or PiZero running NR 3.0.2 but is on NR 3.1.0 on a PiZero 2.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [12 September 2023 09:59 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/5 "2023-09-12T09:59:13Z")

</div>

[messages with `msg.reset` is allowed through the **delay** node · Issue #4337 · node-red/node-red (github.com)](https://github.com/node-red/node-red/issues/4337)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 September 2023 16:09 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/6 "2023-09-12T16:09:54Z")

</div>

Can confirm. Using 3.1.0 on Windows 11/Edge. From the example flow, having issued a couple of the injects, clicking the reset inject does NOT let the first msg through but it then DOES let subsequent reset messages through.

---

<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:** [11 November 2023 16:10 UTC](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221/7 "2023-11-11T16:10:51Z")

</div>

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