NodeRed with node-red-contrib-mikrotik will crash, when component is used after "split" module and execute in cycle

NodeRed with node-red-contrib-mikrotik will crash, when component is used after "split" module and execute in cycle:

node-red  | 17 Mar 08:19:49 - [error] RosException: Timed out after 10 seconds
node-red  |     at Connector.onTimeout (/data/node_modules/node-routeros/dist/connector/Connector.js:188:30)
node-red  |     at Object.onceWrapper (node:events:632:28)
node-red  |     at Socket.emit (node:events:518:28)
node-red  |     at Socket._onTimeout (node:net:595:8)
node-red  |     at listOnTimeout (node:internal/timers:581:17)
node-red  |     at process.processTimers (node:internal/timers:519:7)

When mikrotik module is running once (not in cycle) it works. When it runs inside cycle, few iterations is working and then "mikrotik" module is goying to error, which will destoy whole instance of node-red.

I tried to use "catch" module to prevent crash node-red, but it didn't helped. I tried also close "msg" object in function after split before input into "mikrotik" module, but also it didnt helped.

Thanks a lot for an each help.

Have tried rate limiting (delay node rate mode) or using a queuing node after the split?

Queuing node note, I'm goying to try

delay node rate mode - how can I make rate limiting?

I don't have queue in my modules "palette", you mean this module?

node-red-contrib-simple-message-queue

Thanks a lot @E1cid

The delay node has a rate mode check the dropdowns in the config.
There are examples on this forum of how to set it up to queue messages. using msg.flush. Read the sidebar help text.

This node also queues node-red-semaphore-plus (node) - Node-RED

@E1cid If you were a woman, I would kiss you :smiley: It seems to be, that it helped! Thanks a lot for your help!