Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Setting to allow resending dead letter messages back in to same queue #1659

Open
1 task done
Cave-Johnson opened this issue Mar 4, 2024 · 1 comment
Open
1 task done
Assignees
Labels
💟 Community involvement A feature that the community is invloved with Feature Request New feature or request

Comments

@Cave-Johnson
Copy link

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).

  • 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
@Cave-Johnson Cave-Johnson added Feature Request New feature or request 💟 Community involvement A feature that the community is invloved with labels Mar 4, 2024
@yanivbh1
Copy link
Contributor

yanivbh1 commented Mar 4, 2024

Excellent suggestion, @Cave-Johnson. It will be incorporated into the roadmap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💟 Community involvement A feature that the community is invloved with Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants