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.
In brief
- Hitting the memory limit causes an automatic stop.
- Uncaught errors in your code create a crash.
- You might have hit the Discord API rate limits.
- Monitor the live log in the panel to find the error.
On this page
Discord Bots guides
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.
Common Errors and Solutions
'Out of Memory' error or exit code 137 in logs
Bot exceeded the RAM limit of the current plan.
Upgrade your plan. Member caching on large servers increases memory consumption.
Process closes suddenly, no error code
An uncaught exception or an unhandled promise rejection.
Add error listeners (e.g. unhandledRejection) to your code to log the detail and fix the issue.
Rate limit warnings or 429 errors
Too many requests made to the Discord API in a short time.
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.
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?#
Open the live log
Open the live log in the panel and read the last lines before it stopped.
Identify the error
Write down the exact error, do not guess.
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.
Was this guide helpful?
Feedback goes straight to the team that maintains this guide.
Could not find a solution?
You can open a request with our support team from the panel.