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

API Too many requests, please try again later #5469

Closed
mattiason opened this issue Apr 18, 2022 · 3 comments
Closed

API Too many requests, please try again later #5469

mattiason opened this issue Apr 18, 2022 · 3 comments
Labels
bug Something isn't working stale

Comments

@mattiason
Copy link

mattiason commented Apr 18, 2022

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. I tried to add about 160 items via API Post with a delay of about 500 ms per item with is well within the limit of 10 per soned via API. I have both tried on your hosted environment and on our own hosted

Expected behavior
Be able to add via API Post
Screenshots
image

I have tried both via postman and via the API Reference tool

@mattiason mattiason added the bug Something isn't working label Apr 18, 2022
@panoti
Copy link

panoti commented Jul 7, 2022

The same as me. I also try to add API_REQ_LIMIT_PER_SEC: 1000 into app-service env follow this issue #5679 but can not resolve above error.


When I find the cause of error, I found ysocorp/koa2-ratelimit#39. The function async _hit(key, options, weight) not reset the counter when reached TTL. So we should wait for koa2-ratelimit release new ver or we add an env variable to skip rare limit check?


May this pull request ysocorp/koa2-ratelimit#44 include the fix. Just update koa2-ratelimit package to ver 1.1.1.

brocococonut added a commit to brocococonut/budibase that referenced this issue Jul 13, 2022
Update koa2-ratelimit as per Budibase#5469 to _hopefully_ fix ratelimit not being reset after the set interval.
@smitsialis
Copy link

I am also having this issue. It seems to be tied to the current user. If I use a token from a different user it works (have not pushed more than 100 records). Is there a way to reset this for the user having issues (workaround)? I tried restarting the docker and even upgraded it and still get "too many request" for that user, even for a single GET. Running v 1.1.21.

@stale
Copy link

stale bot commented Sep 26, 2022

This issue has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the stale label Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale
Projects
None yet
Development

No branches or pull requests

4 participants