Retry Loops rate limits - #6460
Merged
Merged
Conversation
Back off and retry 429 responses in web and Stripe delivery paths.
✅ Deploy Preview for old-char ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Loops allows 10 API requests per second. Retry 429 responses with bounded backoff in both web and Stripe senders so lifecycle batches complete cleanly without duplicate mail.
Note
Low Risk
Bounded retries on external email API calls with unchanged success/error semantics and idempotency headers; no auth or data-model changes.
Overview
Adds automatic retry for Loops HTTP 429 responses in both the Stripe and web Loops senders, so lifecycle/transactional batches can finish when the API hits its ~10 req/s limit without manual reruns.
Each sender now loops up to 3 retries after a 429, waiting from the
Retry-Afterheader (default 1s, capped at 5s) while reusing the same POST payload andIdempotency-Key. 200 and 409 (already processed) still exit successfully; other errors behave as before.Tests assert a 429 followed by success results in two requests.
Reviewed by Cursor Bugbot for commit cc88f61. Bugbot is set up for automated code reviews on this repo. Configure here.