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

Identify Failures From Rate Limiting #137

Open
tao-qian opened this issue Mar 5, 2024 · 0 comments
Open

Identify Failures From Rate Limiting #137

tao-qian opened this issue Mar 5, 2024 · 0 comments

Comments

@tao-qian
Copy link

tao-qian commented Mar 5, 2024

Hi!

We have a cron job that runs every evening syncing the chat configuration for all of our users. We saw that some of these requests would fail because of 429, according to the log available in the Stream dashboard
Screenshot 2024-03-05 at 2 13 41 PM

I tried to repeatedly calling the following code to reproduce the rate limiting

 response = channel.update_partial({
    'name' => name,
    'image' => image,
 })
puts response

I was able to get the 429s to show up in the dashboard, but the responses being printed out don't seem to be any different from the normal ones. There was no exception being thrown by the SDK either, which I think would have been the better way for handling failed requests.

What's the recommended way to check if individual requests have failed because of rate limiting based on the response?

Thanks!

@tao-qian tao-qian changed the title Check Failures From Rate Limiting Identify Failures From Rate Limiting Mar 5, 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

1 participant