# Delay node set to rate limit omits messages unexpectedly in case of bursts

**URL:** <https://discourse.nodered.org/t/delay-node-set-to-rate-limit-omits-messages-unexpectedly-in-case-of-bursts/76503>\
**Category:** General\
**Created:** [13 March 2023 09:47 UTC](https://discourse.nodered.org/t/delay-node-set-to-rate-limit-omits-messages-unexpectedly-in-case-of-bursts/76503 "2023-03-13T09:47:45Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [13 March 2023 15:16 UTC](https://discourse.nodered.org/t/delay-node-set-to-rate-limit-omits-messages-unexpectedly-in-case-of-bursts/76503/3 "2023-03-13T15:16:46Z")

</div>

A similar question has been raised [before](https://discourse.nodered.org/t/delay-node-with-rate-limit-by-x-msg-x-time-unit/74427), without a final answer. I think what you see is the result of how the `delay` node is designed to interpret "rate limit." A rate of (x messages per y minutes) is interpreted as 1 message every y/x minutes. Regardless of how many messages are received, they will not be transmitted less than y/x minutes apart. You can select x and y however you like, but as long as the ratio is constant, the result will be the same. There are other ways you could interpret "rate limit," but this one was chosen, and it is as reasonable as any other.

---

_[View the full topic](https://discourse.nodered.org/t/delay-node-set-to-rate-limit-omits-messages-unexpectedly-in-case-of-bursts/76503)._