-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: Support for retrying to deliver SQS message #304
Conversation
d98c89f
to
64a3b50
Compare
16c6a5d
to
a3b40a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Suggestion: make the retry policy a function instead returning visibility timeout. That way a consumer can have their own backoff logic by changing that function. Ie if someone wants to do less or more aggressive backoff like linear or exponential. The function can also take exception as parameter allowing the consumer to change the logic depending on the error.
a3b40a3
to
909c3e6
Compare
909c3e6
to
5a4bbb0
Compare
# [6.2.0](v6.1.4...v6.2.0) (2024-08-29) ### Features * Support for retrying to deliver SQS message ([#304](#304)) ([08bd12a](08bd12a))
🎉 This PR is included in version 6.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
https://linear.app/tibber/issue/INVO-636/retry-when-failing-to-send-email