@alvinmattallen no, not really, or at least nothing that’s likely to have a direct impact. I mean, you should definitely be watching your bot for signs it’s being warned of a ban so that you can address whatever issue there is before they ban an entire IP address, but that’s probably only relevant to a few bots overall. There isn’t a single project, or even a small group of projects that we can pin down as the culprit for triggering a ban, and this is an automated process that they’re unlikely to change on Discord’s side of things.
I have gotten this error,
(node:9969) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
at timeout.client.setTimeout (/rbd/pnpm-volume/56331746-8c95-4640-9930-e44692348b7d/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/ClientManager.js:40:57)
at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/56331746-8c95-4640-9930-e44692348b7d/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/Client.js:434:7)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)
at Timer.processTimers (timers.js:223:10)
(node:9969) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 7)
(node:9969) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I get the same error, it registers the “console logs” well, but when it loads the commands or logs it stops (it does not give any type of error and I have not changed anything since then) nor is it due to errors in the programming of the bot.)
(node:721) UnhandledPromiseRejectionWarning: Error: Something took too long to do.
9:07 PM
at timeout.client.setTimeout (/rbd/pnpm-volume/07e6f2e6-ec3f-483c-ae32-72d1bb1379cf/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/ClientManager.js:40:57)
9:07 PM
at Timeout.setTimeout [as _onTimeout] (/rbd/pnpm-volume/07e6f2e6-ec3f-483c-ae32-72d1bb1379cf/node_modules/.registry.npmjs.org/discord.js/11.5.0/node_modules/discord.js/src/client/Client.js:434:7)
9:07 PM
at ontimeout (timers.js:498:11)
9:07 PM
at tryOnTimeout (timers.js:323:5)
9:07 PM
at Timer.listOnTimeout (timers.js:290:5)
9:07 PM
(node:721) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
9:07 PM
(node:721) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Yeah, of course. It say “something took too long to do”. But after i check the error after it, there’s something error in the package make the project went down. Sorry, i didn’t check the error clearly.
This issue just happened for me.
My project is colossal-butterfly,
I tried resetting the project and updating my packages but nothing seems to work for me.