Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Identify Failures From Rate Limiting #137

Open
@tao-qian

Description

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /