Reading bot logs and fixing common errors
Last updated: 8 November 2026
Open Manage Bots → View Logs. You will see:
- Output: everything your bot prints, plus start-up messages from the server.
- Errors: Python tracebacks and other error output.
Clear logs empties both. Logs from before a restart are kept until you clear them.
Common errors and fixes
| Message | What it means | Fix |
|---|---|---|
409 Conflict: terminated by other getUpdates request |
The same token is running somewhere else. | Stop the bot on your computer or other host. |
401 Unauthorized |
The token is wrong or was revoked. | Put the new token in .env as BOT_TOKEN and restart. |
ModuleNotFoundError |
A package is not installed. | Add it to requirements.txt and install. See packages. |
| Main entry file not found | No bot.py, main.py or app.py in the folder. |
Rename your main file, or move it out of a sub-folder. |
| Bot process exited (code 1) | Your code crashed. It restarts automatically. | Read the Errors log for the line that failed. |
Killed / MemoryError |
The bot used more than 256 MB of memory. | Load less data into memory, or use lighter libraries. |
The bot is "Running" but does not reply
- Check the Errors log first.
- Make sure your code calls
bot.infinity_polling()(or your library's polling/start function). - Make sure the token in
.envbelongs to the bot you are messaging. - Stopping takes about 10 seconds. Wait for the status to change before starting again.