fix: increase retry delay for throttled api requests #39634
Merged
Conversation
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
Increasing this because of reports that CSV uploads are hitting 429s. (I checked and there are no Retry-After headers, so we should be falling back to the default exponential backoff.) Also brings the implementation in line with the comment :P Before, the comment claimed we were starting at 1s but we were starting at 500ms.
charislam
requested a deployment
to
Studio E2E Tests
GitHub Actions
Waiting
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
6 Skipped Deployments
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
ivasilov
approved these changes
Oct 18, 2025
dshukertjr
pushed a commit
that referenced
this pull request
Oct 22, 2025
Increasing this because of reports that CSV uploads are hitting 429s. (I checked and there are no Retry-After headers, so we should be falling back to the default exponential backoff.) Also brings the implementation in line with the comment :P Before, the comment claimed we were starting at 1s but we were starting at 500ms.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Increasing this because of reports that CSV uploads are failing from throttling. (I checked and there are no Retry-After headers, so we should be falling back to the default exponential backoff.)
Also brings the implementation in line with the comment :P Before, the comment claimed we were starting at 1s but we were starting at 500ms.