Troubleshoot a Python Discord bot that stops or stays offline

Open Console in the game control panel and find the first error from the latest start. Stop a repeated restart loop while investigating. Back up your project before edits; reinstalling does not fix a code or configuration error.

Startup and dependency errors

• Entry file missing: check Startup → Python entry file. The relative path and letter case must match the uploaded file, such as app.py. Remove an accidental outer upload folder or use the correct relative path.
• ModuleNotFoundError: list the required package in your requirements file, check Requirements file points to it, and set Install dependencies on start to 1. The package's installation name may differ from its Python import name. Check your project's documentation.
• Import or installation failure: avoid naming your script discord.py. Check package compatibility with Python 3.13 and use tested dependency versions. Upload source files, not a Windows virtual environment. Share the first installation error with support if a package needs unavailable system libraries.

Login and command problems

For LoginFailure or a missing token, check the private configuration and variable name your code reads. Python does not load .env automatically; projects using it need a loader such as python-dotenv. Never print the token to diagnose this. If exposed, reset it privately in the Discord Developer Portal, update your file and restart.

For disallowed intents, match the intents requested in code with the Developer Portal's Bot settings. Enable only what the bot needs. Privileged intents need the corresponding portal permission; enabling them in one place alone is insufficient. See discord.py's intent guide.

If login succeeds but commands fail, check channel permissions, command registration and your project's event handlers. A heartbeat blocked warning can indicate blocking code: for example, async handlers should use await asyncio.sleep(...) rather than time.sleep(...). See the discord.py FAQ.

Get help

For an out-of-memory stop, compare the panel's memory graph with your plan and recent code changes. Contact support with the error time, entry filename and a redacted traceback. Remove tokens and other secrets from logs and screenshots.