Jittered retry backoff + more retries for shared-key workshops#108
Merged
Conversation
Workshops run ~30 participants on a single shared key. The old backoff used fixed delays (5s, 15s) with only 2 retries, so a synchronized burst (everyone clicks Start together) hit 429 and all retried on the same beat — a thundering herd that re-triggered the limit. Add jitter to both fallback and Retry-After waits so concurrent clients fan out, and raise to 5 attempts (4 retries) to ride out transient spikes instead of erroring.
✅ Deploy Preview for ai2aichat 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.
Problem: ~30 participants on one shared key. Old backoff = fixed 5s/15s delays, 2 retries. A synchronized start (instructor says 'go') → all hit 429 → all retry on the same beat → thundering herd that re-triggers the limit, and 2 retries isn't enough to ride out a sustained spike.
Fix:
[2s, 6s, 15s, 30s]so transient bursts self-heal rather than surfacing an error.Note: this absorbs bursts — it does not raise the provider's hard per-key limit. See operational guidance (key tier + fast model). Tests 8/8 ✓, build ✓.