Repository navigation
Add Notification Retry Backoff Configuration #707
Description
Activity
@Henrichy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hi! I'd like to work on this issue.
I've contributed to Rust, TypeScript, backend, frontend, and smart contract projects, with a focus on delivering focused, well-tested changes. I'll keep the implementation within the requested scope, preserve existing behavior unless the issue requires otherwise, include the necessary tests and documentation, and submit a PR that's straightforward to review.
Portfolio: https://portfolio-sandy-alpha-29.vercel.app • ETA: ~2–4 hours.ℹ️ Repo Maintainers: To accept this application, review their application or assign @Henrichy to this issue.
@Abd-Standard please assign this to me. Im short of issues please. Would deliver in less than 2 hours
Congratulations, @olalois! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @olalois: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
@Faith3112 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
please can you kindly assign this issue to me
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Faith3112 to this issue.
@Abayomi7980 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hello Maintainers,
My name is Samuel, and I’m a Full-Stack and Blockchain Developer with over 3 years of professional experience. I’ve reviewed the issue and its requirements, and I’m confident in my ability to implement a reliable solution within the expected timeframe.
I would appreciate the opportunity to work on this issue and contribute to the project. Kindly consider assigning it to me.
Thank you.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abayomi7980 to this issue.
@tizzy005 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hello Maintainer, I’ve carefully reviewed the issue and its requirements. I’m confident I can implement a clean and effective solution that meets the acceptance criteria. Kindly assign it to me.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @tizzy005 to this issue.
@larondo1234 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I’d like to work on this issue because configurable retry backoff can improve notification reliability and reduce unnecessary failures. I’m interested in implementing it cleanly and testing the retry behavior thoroughly.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @larondo1234 to this issue.
@Ghostcecode has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hello Maintainer, I’d love to take ownership of this issue and submit a high-quality pull request once completed I will be glad if this is assign to me.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ghostcecode to this issue.
@araoyeidris16-ctrl has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
IDR NOVA will be active to fix this issue
Pls kindly assign for a better experience with usℹ️ Repo Maintainers: To accept this application, review their application or assign @araoyeidris16-ctrl to this issue.
@JesseJohn7 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
i would like to work on this issues
ℹ️ Repo Maintainers: To accept this application, review their application or assign @JesseJohn7 to this issue.
@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi maintainer, I'd like to work on this issue
ℹ️ Repo Maintainers: To accept this application, review their application or assign @SamixYasuke to this issue.
@dantebalor has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I can deliver quality work and would appreciate the opportunity to contribute to this issue please
ℹ️ Repo Maintainers: To accept this application, review their application or assign @dantebalor to this issue.
@Stormzy-prog has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Allow me to professionally implement this task with precision and accuracy.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Stormzy-prog to this issue.
@hauwauyahass-byte has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Interested in working on this issue. I understand the requirements and can deliver a solution that meets the expected outcome.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @hauwauyahass-byte to this issue.
@CodeMayor has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I'd like to work on this issue because hardcoded retry backoff makes notification providers brittle in production different environments need different delay profiles. Adding configurable, validated backoff parameters with bounded delays is a clean, well-scoped improvement. I can deliver the config struct, validation, tests, and documentation within 48 hours.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @CodeMayor to this issue.
@wavyboy-build has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Dear maintainer, please assign this issue to me
ℹ️ Repo Maintainers: To accept this application, review their application or assign @wavyboy-build to this issue.
Congratulations, @wavyboy-build! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @wavyboy-build: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
🎉 This issue has been marked as completed on GrantFox!
@wavyboy-build's PR #816 was approved and merged by @Abd-Standard.
🏆 @wavyboy-build: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (939 total points). Track your full progress on GrantFox.
👏 Great work, @wavyboy-build! Keep contributing to Core-Foundry.
Description
Allow retry backoff behaviour to be configured independently of the notification provider implementation.
Acceptance Criteria
Backoff parameters are configurable.
Invalid values are rejected.
Retry delays remain bounded.
Configuration is documented.