You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our API offers a delayed requeue where it is possible that the error is transient and could be fixed by simply returning to the queue with a delay. There are three responses we have:
Native support for requeue with delay; we used this
No native support for requeue and we requeue via a timer event that posts after the elapsed time window
We block for the delay period then requeue
We know that 3 is never the right solution as this will block the whole pump, and pause message processing, not requeue with a delay. We should fix those transports that have the incorrect behavior.
Further technical details
The internal message consumer is a good example of how to get this right with a internal Requeue method that is called via a timer if delay is requested, and just passed through if not.
The text was updated successfully, but these errors were encountered:
Describe the bug
Our API offers a delayed requeue where it is possible that the error is transient and could be fixed by simply returning to the queue with a delay. There are three responses we have:
We know that 3 is never the right solution as this will block the whole pump, and pause message processing, not requeue with a delay. We should fix those transports that have the incorrect behavior.
Further technical details
The text was updated successfully, but these errors were encountered: