Skip to content

Handle rate limit errors by respecting X-RateLimit-Reset and Retry-After headers and returning cached queue length #7683

Description

@andrewhibbert

Proposal

The best practices suggest to handle rate limit errors appropriately, in particular:

  • If the retry-after response header is present, you should not retry your request until after that many seconds has elapsed.
  • If the x-ratelimit-remaining header is 0, you should not make another request until after the time specified by the x-ratelimit-reset header. The x-ratelimit-reset header is in UTC epoch seconds.

Use-Case

Continuing to make requests while you are rate limited may result in the banning of your integration.

Anything else?

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Ready To Ship

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions