Repository navigation
[Quality-2][High] Add bounded retry policy to external provider calls #940
Description
Summary
Implement Add bounded retry policy to external provider calls as a production-ready change in Predictify-org/predictify-backend.
Why this matters
The implementation must be deterministic and reviewable so normal operation and adverse conditions do not cause silent data loss, inconsistent state, security regressions, or an unrecoverable user experience. This issue specifically requires retries, duplicates, timeouts, and partial failure safe and observable.
Scope
Trace the relevant entry points, state model, and failure paths; implement the smallest complete design; preserve public interfaces unless a compatibility plan is included; and document important invariants in code.
Priority
High
Acceptance criteria
- The intended behavior is deterministic for valid, invalid, duplicate, and boundary-case inputs.
- Authorization, validation, and state-transition invariants remain enforced.
- Retries, partial failure, and concurrent execution cannot produce an unsafe or inconsistent result.
- Focused tests cover success, rejection, boundary, and regression scenarios.
- Existing callers remain compatible, or the PR includes a tested migration path.
- Relevant logs, metrics, or user-visible errors make failures diagnosable without exposing sensitive data.
Validation
Run focused tests and repository CI checks with evidence for normal operation, invalid input, retries, concurrency or timing boundaries, and failure recovery where applicable.
Non-goals
- Typo-only, formatting-only, documentation-only, or cosmetic changes.
- Unrelated refactors, dependency upgrades, or broad rewrites.
- Removing safeguards or weakening validation to make tests pass.
Contributor application
Before coding, describe affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.
PR requirements
Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.
Quality review
A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.
Activity
TheShnider commentedon Aug 28, 2026
@TheShnider has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheShnider to this issue.
drips-wave commentedon Aug 28, 2026
Congratulations, @TheShnider! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @TheShnider: 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 🌊
feat: Add bounded retry policy to external provider calls, Closes #940 (
grantfox-oss commentedon Aug 29, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!
@TheShnider's PR #944 was approved and merged by @greatest0fallt1me.
🏆 @TheShnider: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,206 total points). Track your full progress on GrantFox.
👏 Great work, @TheShnider! Keep contributing to Predictify-org.
drips-wave commentedon Aug 29, 2026
This issue has been completed by @TheShnider as part of the Stellar Wave Program's 8th Wave 🥳
😎 @TheShnider: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Fix 937 normalize api pagination and validation errors (#945)
Issue 936 (#947)