The SQS transport supports delayed delivery of messages for longer than 15 minutes (900 seconds) in versions 4 and above.
Enable unrestricted delayed delivery
In NServiceBus.AmazonSQS version 6 and higher the unrestricted delayed delivery feature is enabled by default. In order to work, it has to be enabled in both the sender and the receiver. When communicating with endpoints running older version of the transport ensure that it is enabled.
Unrestricted delayed delivery must be enabled on the sender and receiver to be able to delay messages longer than 900 seconds.
|delay duration <= 900 sec||disabled||disabled||Yes|
|delay duration > 900 sec||disabled||disabled||No|
Unrestricted delayed delivery requires a FIFO queue for each endpoint that receives delayed messages. The transport handles creation of the FIFO queue automatically when installers are enabled.
Manual FIFO queue creation
If installers are not used, then the FIFO queue will need to be manually created.
The FIFO queue has the following requirements:
- The name must match the endpoint's input queue suffixed with
- The Delivery Delay setting (DelaySeconds) should be set to 900 seconds.
- The Message Retention Period should be set to at least 4 days.
- A Redrive Policy must not be configured.
For an example of how to manually create queues, see scripting.
How it works
When a delayed message is sent, the delay duration is calculated. If it's less than or equal to 900 seconds, the message is sent directly to the destination input queue with the
DelaySeconds message attribute set to the delay duration.
If the delay duration is greater than 900 seconds, then the message is sent to the destination's FIFO queue with the
NServiceBus. custom message attribute set to the delay duration. When the message is received from the FIFO queue after 900 seconds, the remaining delay duration is calculated. If it's less than or equal to 900 seconds, the message is forwarded to the destination input queue with the
DelaySeconds message attribute set to the remaining delay duration. Otherwise, the message is sent back to the FIFO queue with an updated custom message attribute set to the remaining delay duration.
The following sequence diagram illustrates a message sent with a delay duration greater than 900 seconds:
Potential duplicate messages
While FIFO queues protect from message duplication, there are still scenarios where messages could be duplicated. To address the possibility of duplicate messages, handlers should be idempotent or the outbox feature should be enabled.
As the final step, the message has to be delivered to a regular queue.
While processing a message, if a failure prevents the message from being deleted, and the next processing attempt occurs later than 5 minutes after the first attempt, then the FIFO queue will not be able to protect from message duplication.
Delay of 14 minutes and 5 seconds
Delay of 32 minutes and 5 seconds
Enabling unrestricted delayed delivery will have an impact on cost because FIFO queues are required.
To estimate the cost of a delayed message, the following formula can be used:
N = delay in seconds
P = price per request
C(ycles) = N / 900
O(perations) = C * 2 // dequeue and requeue
T(otal cost) = O * P
To calculate the cost of a single message delayed for a year, the following applies:
Price per 1 Million Requests after Free Tier (Monthly)
FIFO Queue: $0.50 ($0.00000050 per request)
N = 31,536,000 seconds
P = $0.00000050
C = 31,536,000 / 900 = 35,040
O = 35,040 * 2 = 70,080
T = 70,080 * $0.00000050 = $0.03504