# Delay node behaviour change on reset message

**URL:** <https://discourse.nodered.org/t/delay-node-behaviour-change-on-reset-message/82154>\
**Category:** General\
**Created:** [18 October 2023 10:01 UTC](https://discourse.nodered.org/t/delay-node-behaviour-change-on-reset-message/82154 "2023-10-18T10:01:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [18 October 2023 11:17 UTC](https://discourse.nodered.org/t/delay-node-behaviour-change-on-reset-message/82154/3 "2023-10-18T11:17:43Z")

</div>

I raised this issue,

It has since been fixed, but not sure if its released yet, but its already known (and is fixed in code)

> [@Has something changed with the delay node?](https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221):
>
> Hello everyone, its been a while sweat_smile 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 intende…

> <https://github.com/node-red/node-red/issues/4337>
>
> \### Current Behavior
> 
> When the delay node is configured as.
> 
> - Rate Limit
> … 
> And
>  
> - No messages are currently held back.
>   
> 
> Messages containing \`msg.reset\` are being passed through 
> 
> \### Expected Behavior
> 
> It appears this is new behaviour, and previously, \`msg.reset\` has never been passed through, as it should be a control message.
> 
> I'm unsure if this is now expected behaviour, or something has gone pop! 
> 
> \### Steps To Reproduce
> 
> - Set Delay node to \`Rate Limit\`
> - send it a message with \`msg.reset\`
>  
> See that it passes the messages through.
> 
> \### Example flow
> 
> \`\`\`
> \[{"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"\]\]}\]
> \`\`\`
> 
> 
> \### Environment
> 
> \- Node-RED version: 3.1.0 (but I cant help thinking I noticed this change a little before)
> 
> Not at my workstation currently, but this is discussed below also:
> 
> https://discourse.nodered.org/t/has-something-changed-with-the-delay-node/81221

---

_[View the full topic](https://discourse.nodered.org/t/delay-node-behaviour-change-on-reset-message/82154)._