View logs and debug a crashing bot

Your bot's logs are its live Console in the panel — everything it prints to stdout/stderr shows up there in real time, and stays visible until the next restart. When a bot will not stay up, the answer is almost always in the last few lines before the process exited. This guide shows how to read them and fix the usual causes.

Read the Console the right way

• Open the bot and look at the Console tab — it streams live output while the server runs.
• When a bot crashes you will see a line like "process exited with code 1" — scroll up from there to the real error (a stack trace, a rejected promise, an import error).
• Restart to reproduce cleanly: the Console clears the visible buffer on start, so you get the crash from the top without old noise.
• Copy the error text (redacting any token) when asking for help — the exact message matters.

The usual crash causes

Get more detail from your bot

// Node.js — surface the errors that usually kill a bot silently
process.on('unhandledRejection', (err) => console.error('UNHANDLED REJECTION:', err));
process.on('uncaughtException', (err) => console.error('UNCAUGHT EXCEPTION:', err));

client.on('error', console.error);
client.on('warn', console.warn);

# Python — enable discord.py's logging to the console
import logging
logging.basicConfig(level=logging.INFO)