This repository was archived by the owner on Jul 11, 2024. It is now read-only.
This repository was archived by the owner on Jul 11, 2024. It is now read-only.
Open
Description
Describe the bug
A rate limit exceeded error can occur if a certain endpoint shares the rate limit bucket with another endpoint but disgord doesn't know it yet. For example, if I react on a message and immediately unreact, the unreact fails because it shares the bucket with react. Example bot: gist.
I'm hesitant to call this a bug because I understand that this is how Discord works and it is not possible to know the bucket in advance, but it would be nice if the request could be auto-retried if, for instance, it fails due to 429 and its bucket was previously unknown. I will have to manually implement a retry anyway if disgord doesn't do it.