Reading logs (even if you're not a developer)
Every line of text your bot prints to the screen (the console) while running is a log. The Logs section on the bot page shows the latest lines in real time. It's the fastest way to find a problem.
If you're not a developer
Logs can look intimidating at first, but you don't need to understand them fully — your job is to find the right part and show it to an AI (or your developer).
What to look for
- A line starting with
Traceback (most recent call last):means a Python error started here. Copy everything from that line to the very end. - The words
Error,Exception,Unhandled rejectionmean something went wrong. - The very last line is usually the short name of the error (e.g.
ModuleNotFoundError: No module named 'requests') — often the most important line.
How to show logs to an AI
Copy a few dozen lines around the error and write something like: "My bot on Botxona isn't working, here are the logs: [copied text]. Explain the problem and give me the fixed code." The AI usually pinpoints the cause.
Crash-loop — when the bot crashes again and again
If the bot stops with an error right after starting, the system automatically tries to restart it. But if the bot crashes more than 5 times within 10 minutes, the system treats it as a "crash-loop" and stops retrying — the bot's status changes to "crashed" and you get a notification. This keeps endless restarts from wasting server resources.
In that case: read the logs, find the cause (most often a wrong token, a missing library or an error in code that runs at startup), fix the code and redeploy.
Next step
The most common errors and their fixes: Errors and fixes.