Error: Shard 0's Client took too long to

(node:2731) UnhandledPromiseRejectionWarning: Error: Shard 0’s Client took too long to become ready.

10:30 PM

at Timeout._onTimeout (/rbd/pnpm-volume/8d24d1f7-a978-48f5-8f12-9d53c2bfeb01/node_modules/.registry.npmjs.org/discord.js/11.6.2/node_modules/discord.js/src/sharding/Shard.js:89:31)

10:30 PM

at listOnTimeout (internal/timers.js:531:17)

10:30 PM

at processTimers (internal/timers.js:475:7)

10:30 PM

(node:2731) 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: 1)

10:30 PM

(node:2731) [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.

TR: Böyle bir Hata Alıyorum Bilen Varsa Lütfen Ulaşsın

Welcome To The Community @Erengzl!
Unfortunately sharding would be an issue due to the memory limit of glitch and the other limits.
I see there is a issue with a promise rejection. Do by any chance have a error handler for unhandled rejections? if not then this could potentially resolve where the error is coming from?
process.on("unhandledRejection", err => { system.log(err.stack, "error"); });