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

"Too many requests" when sending a review/comment and a rating #407

Open
vankasteelj opened this issue Jun 12, 2023 · 1 comment
Open

"Too many requests" when sending a review/comment and a rating #407

vankasteelj opened this issue Jun 12, 2023 · 1 comment

Comments

@vankasteelj
Copy link

Hi, I recently introduced comments/reviews on my own app based on trakt api, by displaying a popup that said "you watched X episodes of this show, would you rate and review it?" or "you watched this movie, would you rate and review it". Sadly, it often errors with a 429 "Too many requests" because I try to simultaneously send a comment and a rating (there's probably a few ms here and there for V8 to process the two requests, but still, it's "almost" simultaneous).

Would you consider adding a way to add a rating to a comment and/or disabling the rate limit on some call, maybe /rate and /comment specificaly? I cant be the only one that sees the common denominator in those two calls.

In the meantime, I will introduce a 1sec delay between the two requests, but still, it's annoying :) Thanks!

@kevincador
Copy link

Hey @vankasteelj,

I have had the same kind of issue in my app. Instead of introducing a delay, I'm looking at the "retry" info int he response and I retry after the amount of time that info gives me. IMO it's better that way because it's not working on some hardcoded artificial delay. I'm of course never showing a 429 to the end user, it's just use internally to know I have to queue the request and restart after X.

Cheers,

Kevin

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