The console gives a lot of logs- nearly 3 to 4 each second, throughout a period of about 10 minutes. This means almost 2000 errors.
It only actually logs 1 to 10 in the logging channel before it starts a 60-second cooldown timer (which might be resetting every time a new crash happens?; that would be a bug too technically)
Perhaps add a time.sleep() if it crashes, or after every x errors
2023-07-13 18:49:58 WARNING discord.http We are being rate limited. GET https://discord.com/api/v10/channels/1019562983757729903/messages responded with 429. Retrying in 0.69 seconds.
We are being rate limited. GET https://discord.com/api/v10/channels/1019562983757729903/messages responded with 429. Retrying in 0.69 seconds.
It only raises the warning for /channels/0123456789012345678/messages, and always with a relatively short retry timer below 1 second (which sounds odd because it retries more than 2 times a second, although that shouldn't be happening/possible)
The timer is usually around the same milliseconds as the errors around it, but do vary about 0.05 in any direction (usually decrementing, which is logical)
The console gives a lot of logs- nearly 3 to 4 each second, throughout a period of about 10 minutes. This means almost 2000 errors. It only actually logs 1 to 10 in the logging channel before it starts a 60-second cooldown timer (which might be resetting every time a new crash happens?; that would be a bug too technically)
Perhaps add a time.sleep() if it crashes, or after every x errors
It only raises the warning for /channels/0123456789012345678/messages, and always with a relatively short retry timer below 1 second (which sounds odd because it retries more than 2 times a second, although that shouldn't be happening/possible)
The timer is usually around the same milliseconds as the errors around it, but do vary about 0.05 in any direction (usually decrementing, which is logical)