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.

Einsteiger4 minAktualisiert:5. Oktober 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.

Fehlerbehebung

Symptom

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

Ursache

Bot exceeded the RAM limit of the current plan.

Lösung

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

Symptom

Process closes suddenly, no error code

Ursache

An uncaught exception or an unhandled promise rejection.

Lösung

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

Symptom

Rate limit warnings or 429 errors

Ursache

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

Lösung

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.

War diese Anleitung hilfreich?

Feedback geht direkt an das Team, das diese Anleitung pflegt.

Keine Lösung gefunden?

Sie können im Panel eine Anfrage an unser Support-Team senden.

Supportanfrage öffnen