Bot Panel: logs and diagnostics - why a bot does not work
Logs
The Logs tab shows bot output live. Filter: All, Errors, Warnings, Watchdog, plus a line search. "Autoscroll" keeps the newest lines in view, "Download" saves the log to a file, "Clear" clears the window.

If the bot crashes, the error text is in the log - start there. Only recent lines are kept, so logs never fill up the disk.
Diagnose
Diagnose tab - "Check" button. The panel checks whether the token is set and accepted by Telegram, whether there is a dependency file and a .env file, and whether the bot is running.

Common causes
| Symptom | What to do |
|---|---|
| Token missing or invalid | set the token in Config Vars and verify it with "Check token" |
ModuleNotFoundError / Cannot find module in the log | the library is missing from the dependency file - add it and click "Install dependencies" |
Conflict: terminated by other getUpdates request | the same bot is running somewhere else (on your computer or another server). Stop the other copy |
| The bot keeps restarting | memory limit exceeded - raise the RAM limit in the Overview tab |
| Code changes have no effect | click "Restart" after saving |