Skip to content

fix(frontend): retry with exponential backoff + fee cache for Horizon 429s (#667)#733

Open
AnnabelJoe wants to merge 1 commit into
Haroldwonder:mainfrom
AnnabelJoe:fix/667-horizon-rate-limit-retry
Open

fix(frontend): retry with exponential backoff + fee cache for Horizon 429s (#667)#733
AnnabelJoe wants to merge 1 commit into
Haroldwonder:mainfrom
AnnabelJoe:fix/667-horizon-rate-limit-retry

Conversation

@AnnabelJoe
Copy link
Copy Markdown

Closes #667

Problem

fetchRemittanceFee had no handling for HTTP 429 (Too Many Requests) from the Horizon API. Under load, callers received errors instead of a usable fee estimate.

Fix

  • Retries up to 3 times with exponential backoff (500ms, 1s, 2s) on 429 responses.
  • Caches the last successful fee per remittance ID in a Map and returns the cached value when all retries are exhausted.

@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 1, 2026

@AnnabelJoe is attempting to deploy a commit to the Harold's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Jun 1, 2026

@AnnabelJoe Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

horizonService.ts fetchRemittanceFee does not handle Horizon API rate limiting

1 participant