No retry policy exists for financial mutations, so a single transient 503 fails the whole flow

[K1NGD4VID]

Category: Functional Edge Case

Repository location: apps/web/lib/api.ts, apps/web/hooks/useInvoices.ts, apps/web/hooks/usePool.ts, apps/web/hooks/useProfile.ts

Problem
apiFetch special-cases 503/504 with a friendlier "Service Temporarily Unavailable, try again later" message, but no mutation hook (useMutation calls in useInvoices.ts, usePool.ts, useProfile.ts) sets a retry option, and react-query's mutation default is retry: 0. A transient gateway blip on createInvoice, deposit, withdraw, repayInvoice, etc. fails immediately with no automatic recovery, despite the UI copy implying the user should just wait and retry.

Evidence
Grep of apps/web/hooks/*.ts shows no retry: option on any useMutation call; apiFetch's 503/504 branch in apps/web/lib/api.ts (~lines 82-98) only changes the message, not the retry behavior.

Suggested implementation
Add bounded retry with backoff (e.g. retry: 2, retryDelay: exponential) for idempotent mutations, or at minimum surface an explicit "Retry" button in the mutation's error toast that re-invokes mutate with the same variables.

Acceptance criteria

• A mutation that fails with a 503 automatically retries up to N times with backoff before surfacing an error to the user.
• A test simulates a 503-then-200 sequence and asserts the mutation ultimately succeeds without user interaction.

Difficulty: Medium

Expected impact: Reduces user-visible failures caused by transient backend/RPC blips on money-moving actions.

---

Filed as part of the second repository-wide audit (deeper refinements following the first cleanup pass).

[omoniyiadebayo12goal-crypto]

@omoniyiadebayo12goal-crypto has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer,

I’m Omoniyi. I have carefully reviewed the issue description, acceptance criteria, and expected deliverables. Kindly assign me this task.
Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @omoniyiadebayo12goal-crypto to this issue.

[francescoricc1]

@francescoricc1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

LET ME FIX THIS PLEASE

ℹ️ Repo Maintainers: To accept this application, review their application or assign @francescoricc1 to this issue.

[drips-wave]

Congratulations, @francescoricc1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @francescoricc1: 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 🌊