Your Bot Keeps Stopping? What Should You Do?

The most common causes for a bot stopping, and how to fix the problem from your logs.

Principiante4 minActualizado:5 de octubre de 2026

If your bot stops unexpectedly the cause is usually one of three: hitting the memory limit, an uncaught error, or being rate limited by Discord.

Solución de problemas

Síntoma

'Out of Memory' error or exit code 137 in logs

Causa

Bot exceeded the RAM limit of the current plan.

Solución

Upgrade your plan. Member caching on large servers increases memory consumption.

Síntoma

Process closes suddenly, no error code

Causa

An uncaught exception or an unhandled promise rejection.

Solución

Add error listeners (e.g. unhandledRejection) to your code to log the detail and fix the issue.

Síntoma

Rate limit warnings or 429 errors

Causa

Too many requests made to the Discord API in a short time.

Solución

Slow down requests, reduce unnecessary API calls and ensure the bot respects rate limit headers.

Uncaught Errors#

An unhandled promise rejection terminates the process. Adding the two listeners below makes your bot log the error instead of crashing.

javascript
process.on("unhandledRejection", (error) => {
  console.error("Yakalanmamış hata:", error);
});

process.on("uncaughtException", (error) => {
  console.error("Beklenmeyen hata:", error);
});

What to Do to Find the Problem?#

1

Open the live log

Open the live log in the panel and read the last lines before it stopped.

2

Identify the error

Write down the exact error, do not guess.

3

Take action

If it is a memory error, upgrade the plan. If it is a code error, fix it and upload again. If you cannot solve it, open a support request from the panel and include the log output.

¿Te ha resultado útil esta guía?

Los comentarios van directamente al equipo que mantiene esta guía.

¿No encontró una solución?

Puede abrir una solicitud al equipo de soporte desde el panel.

Abrir una solicitud