Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seeing 429 response for "too many requests" #48

Closed
pviswanathan opened this issue Jun 12, 2024 · 2 comments
Closed

Seeing 429 response for "too many requests" #48

pviswanathan opened this issue Jun 12, 2024 · 2 comments

Comments

@pviswanathan
Copy link

await new Promise(resolve => setTimeout(resolve, 1000));

I tried to find API doc references to why 429's are issued with no luck. We are able to reproduce the 429 pretty consistently. Might it make sense to extend the timeout between requests to something higher?

@avi12
Copy link
Owner

avi12 commented Jun 12, 2024

You're welcome to implement an exponential backoff algorithm, test that it works and then create a PR and I'll merge it

avi12 added a commit that referenced this issue Oct 1, 2024
- Edge deployment: Added exponential backoff (#48)
- Improved documentations
- `package.json`: Upgraded packages
- Fixed EditorConfig
@avi12
Copy link
Owner

avi12 commented Oct 1, 2024

Added exponential backoff in 0.13.0

@avi12 avi12 closed this as completed Oct 1, 2024
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

No branches or pull requests

2 participants