Say if; The delay node is set to rate limit to 2 messages per every 8 seconds and drop messages. If you send a message every 1 seconds it will send the first message and the 5th message. That's really not what I would expect. (That would be 1 message per every 4 seconds). I would like to suggest …

You could use a batch node along with a switch node to do this. [{"id":"da45394df2146f4a","type":"inject","z":"d1395164b4eec73e","name":"","props":[{"p":"reset","v":"true","vt":"bool"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":210,"y":6840,"wires…

Thanks, I'll have a look at that but I still think this node doesn't really work as expected. As soon as you enter a numeral greater than 1 in the first box it should behave as I explained.

This has been discussed a few times over the years, and while, logically, you may well be correct, such a change in behaviour would be a breaking change (it could cause existing flows to break), which reduces the chance of it being implemented.

It may do but if it's incorrect it shouldn't stay incorrect it should be corrected! I would have thought that few would have used the node as anything other than 1 message per ... unless they had wanted it to behave as I would expect it to behave. After all, who would put 2 messages per 8 seconds i…

[image] Tinbum1: if it's incorrect it shouldn't stay incorrect it should be corrected It isn't a bug, it performs according to the documented spec. Whether it is 'incorrect' is a matter of interpretation.

Yes, thank you. It shouldn't be that complicated though and the logic in the node is wrong. Why does it even have a box to fill in of 'x' messages when it's pointless because of the way the node works at present.?

Reminds me of ISO9000. As long as you conform to the way you say you are going to do it then it's correct even though what you are conforming to is wrong.

[image] Tinbum1: even though what you are conforming to is wrong. As I said, whether the behaviour is wrong is a matter of interpretation. The current behaviour is exactly as documented in the help text. "When configured to rate limit messages, their delivery is spread across the configured…

The meaning of rate limit is not spread over a given time period it is within a time period.The node contains the word 'per' You would put 1 per 0.6 minutes or 1 per 36 seconds.

Delay node- rate limit extension

Core Development Feature Requests

jbudd 1 January 2025 16:31 5

Is this relevant?
https://discourse.nodered.org/t/limit-message-number-per-hour/53724

Topic		Replies	Views
Delay node - rate limit strange behaviour. Confusing limit rates. Is it lying us (a little)? General delay	11	273	26 December 2025
Delay node with rate limit by x msg / x time unit Feature Requests delay , function-node	11	353	7 February 2023
Delay node set to rate limit omits messages unexpectedly in case of bursts General	22	483	16 March 2023
Limit message number per Hour General delay	17	2427	24 November 2021
Delay node - rate limit not working for all messages? General delay	25	385	2 December 2024

Delay node- rate limit extension

Related topics