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
It would be useful to get the ability to resend dead lettered messages to the original queue (in addition to the feature that lets them be sent to a different queue).
It would be good to do this with a configurable time delay ie resend after X minuets.
It would be good to limit the amount of times a dead lettered message gets resent ie gets resent 3 times before it is permanently dead lettered.
Use case I see is that occasionally a consumer will fail to process a message for whatever reason (downstream component it requires is unavailable, some sort of timeout), we don't want to lose the message / data and usually the next time the message is resent, 99% of the time it processes fine. For us, it is extra overhead having a different consumer running just for dead lettered messages in a different station, although this would likely be used if a message failed to be reprocessed after X amount of retries.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Description
It would be useful to get the ability to resend dead lettered messages to the original queue (in addition to the feature that lets them be sent to a different queue).
Use case I see is that occasionally a consumer will fail to process a message for whatever reason (downstream component it requires is unavailable, some sort of timeout), we don't want to lose the message / data and usually the next time the message is resent, 99% of the time it processes fine. For us, it is extra overhead having a different consumer running just for dead lettered messages in a different station, although this would likely be used if a message failed to be reprocessed after X amount of retries.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: