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 of time, so i need to wait for 20 seconds unnecessarily, hence i added a msg.f…

[image] smanjunath211: Note : injecting msg.flush from an inject node without any payload works perfectly. I think you answered you own problem, you have to delete any other properties or in a function node return {flush:1}

Instead of using the complexities of flushing, I would remove the empty items (ie. the items you are not interested in) before the split ?

[image] E1cid: return {flush:1} yes. did the trick!

[image] E1cid: you have to delete any other properties [image] smanjunath211: but there are so many properties, it is difficult to delete all of them (is there a *.* delete for this step?) [image] E1cid: return {flush:1} sequence of events for any future visit

I might try adding a switch node to filter the empty messages first. IE, if msg.payload is empty, have the switch send it to output 1, which is connected to nothing. Then add a rule for "Otherwise" to output two, which then feeds the rate limit. [image]

[image] Rgrove: switch node to filter the empty messages first. the empty 'message' isn't generated until i process the output from the split node first. bulk message--> split -->rate limt-->process-->may be empty/may not be empty-->if empty waits till rate limit is sending next message(this…

[image] smanjunath211: however, some messages are empty, and hence dont take any amount of time, so i need to wait for 20 seconds unnecessarily, I read this as, there is an empty message reaching the rate limit node, and you're adding a flush to remove it. If the empty message is queued by ra…

there is no empty message before the rate limit. all are valid messages, because of the length of the payload incoming, the time taken to process is different for each message, so to avoid conflict in database access, i have given sufficient time (rate limit) to allow the message to process. however…

That is precisely how I have done now by following @E1cid 's instruction. Using a function node to send flush:1 ( I already had the same logic, however, along with flush :1, I was sending bunch of other unintended messages, so it was getting added in queue.

Are you using flush with all messages or just empty ones?

Msg.flush adding message into the queue

General

Colin 17 January 2025 09:40 10

You can use the flow shown here instead of your rate limit -> process. It does not use a fixed rate limit but releases the next message when the previous one has been completed however long it takes, so it will automatically adapt the rate to maximise the throughput.

Topic		Replies	Views
Rate limiting based on exec node completion General	44	1407	2 January 2022
Msg.flush =1 not working to flush rate limit node if connected through link nodes? General rate-limit , link-nodes	5	75	12 March 2025
Can the Delay node rate limit, but pass first message immediately, and always pass on the latest message? General	77	2015	8 November 2022
Possible to listen to debug console and wait until no more messages? General	31	314	20 October 2024
Queuing message and timing. (text to voice stuff) General	22	393	15 December 2023

Msg.flush adding message into the queue

Related topics