# \#rate-limit

**URL:** https://discourse.nodered.org/tag/rate-limit/196.md

[Latest](https://discourse.nodered.org/latest.md) · [Categories](https://discourse.nodered.org/categories.md) · [Tags](https://discourse.nodered.org/tags.md)

---

## [Rate limiter that doesn't delay first message](https://discourse.nodered.org/t/rate-limiter-that-doesnt-delay-first-message/99883)

<div class="topic-metadata">

**Author:** [@scf](https://discourse.nodered.org/u/scf)\
**Replies:** 2\
**Last updated:** [7 December 2025 10:17 UTC](https://discourse.nodered.org/t/rate-limiter-that-doesnt-delay-first-message/99883 "2025-12-07T10:17:54Z")

</div>

I'm looking for a different rate limiter and wonder if anyone has already built it. The default rate limiter seems to delay the first message by the limit rate. I want the first message after deployment to be sent, and …

---

## [Understanding ratelimit per topic](https://discourse.nodered.org/t/understanding-ratelimit-per-topic/98070)

<div class="topic-metadata">

**Author:** [@waquete](https://discourse.nodered.org/u/waquete)\
**Replies:** 5\
**Last updated:** [13 July 2025 10:47 UTC](https://discourse.nodered.org/t/understanding-ratelimit-per-topic/98070 "2025-07-13T10:47:07Z")

</div>

I am confused by the delay / rate limit node, not sure it can do what I want. Here is what I wish to: sending message with different topics (say topic1, topic2). rate limit for each topic (say 1 msg per minute). just…

---

## [Msg.flush =1 not working to flush rate limit node if connected through link nodes?](https://discourse.nodered.org/t/msg-flush-1-not-working-to-flush-rate-limit-node-if-connected-through-link-nodes/95663)

<div class="topic-metadata">

**Author:** [@smanjunath211](https://discourse.nodered.org/u/smanjunath211)\
**Replies:** 4\
**Last updated:** [26 February 2025 12:32 UTC](https://discourse.nodered.org/t/msg-flush-1-not-working-to-flush-rate-limit-node-if-connected-through-link-nodes/95663 "2025-02-26T12:32:58Z")

</div>

Is this expected and known or is a bug? I struggled for so long why my flow is not working, but accidentally found out that the msg.flush works only if DIRECTLY connected to the rate limit node. the two top flows are…

---

## [Allow random range delay](https://discourse.nodered.org/t/allow-random-range-delay/95230)

<div class="topic-metadata">

**Author:** [@eden881](https://discourse.nodered.org/u/eden881)\
**Replies:** 7\
**Last updated:** [8 February 2025 15:08 UTC](https://discourse.nodered.org/t/allow-random-range-delay/95230 "2025-02-08T15:08:05Z")

</div>

I'd love the option to delay & rate-limit messages using a range to select a random amount of time. For example: delay messages to 3-6/sec, so that each message in the queue will wait between 3 to 6 seconds. It helps t…

---

## [Msg.flush adding message into the queue](https://discourse.nodered.org/t/msg-flush-adding-message-into-the-queue/94665)

<div class="topic-metadata">

**Author:** [@smanjunath211](https://discourse.nodered.org/u/smanjunath211)\
**Replies:** 16\
**Last updated:** [17 January 2025 14:24 UTC](https://discourse.nodered.org/t/msg-flush-adding-message-into-the-queue/94665 "2025-01-17T14:24:46Z")

</div>

I have a flow in which there are nearly 20 messages coming from a node and i split them to process individually so i set a rate limit of approx 20 seconds. however, some messages are empty, and hence dont take any amount…