vladfrangu
commented
2 years ago We already handle global and per-route ratelimits in discord.js. Without more context, like what version you're running, what routes you're calling, debug logs etc, we cannot do much...
Depending on your bot size and use case, you might be hitting this limit instead. If that's the case, take a look, inspect your code, see if you handle checks before calling the API, etc.
Jiralite
Which package is the feature request for?
discord.js
Feature
We are running several DiscordBOTs and in the process of running them, we get stuck in the global rate limit of the DiscordAPI and can't access Discord for an hour. It is too difficult for us to solve this problem by ourselves, so we would appreciate it if you could fix it in Discord.js so that it is not stuck by the global rate limit. I await your reply.
Ideal solution or implementation
We operate and develop what is commonly known as global chat, which connects several Discord servers. We have encountered a problem that this BOT gets stuck in the global rate limit, which is a limitation of the Discord API. This limit prevents access to Discord for an hour. So, I would like to see a limit put in Discord.js beforehand.
Alternative solutions or implementations
Resolving this issue will allow developers to maintain safe and rapid BOT development, as the limits can be placed on the Discord.js side before they are caught by the global rate limit.
Other context
The BOT we are developing is sending several messages at the same time to connect registered channels with each other!