Message queues and retries

This section explains how to configure message queues, retries, and sizes, as well as to disable message queues.

Modules in a flow perform an action when a message is received. Sometimes a module is not ready when a message arrives. The cause may be due to an output module waiting on a response from an external system or a processing module that is not done processing the current message.

Each module has a message queue that holds messages waiting to be processed used to resend messages in case delivery fails.

Queue settings

Queue settings control the queue behavior of each module, found on the General tab in the module settings panel. Also available is a global Disable Queues setting in the flow settings panel.

Message retries

Note: The message retry functionality is set on the flow.

Message queues are useful when an output module fails to deliver a message to an external system, keeping the message until successfully delivered.

The following settings control the message retry behavior of modules:

• Max number of retries: Specifies the number of times the module attempts to resend a message delivery fails. This mode is enabled by setting the value higher than 0. If the message remains unsent after the maximum number of retries, the message drops from the queue.

• Minimum Delay Between Successful Messages in Milliseconds [default: 0]: If the external system cannot cope with high message rates, this setting ensures at least a minimum delay between each successful delivery. If the flow produces bursts of messages, increasing this value smooths out external requests.

• Retry Delay in Milliseconds [default: 1000]: This setting introduces a delay between each retry attempt to avoid overloading the external system.