Bot History

Bot History is the operational log for Telegram bot commands connected to your organisation. It shows what ran, when it ran, what status it reached, and enough detail to diagnose unexpected bot behaviour.

Open it from Settings > Telegram > Bot History.

Who can use it

Editors and Admins can view Bot History. Admin-only controls appear for queue recovery and log cleanup.

What you'll see

• Active queue - in-flight bot commands with live status
• Command log - recent commands, status, input, parameters, response JSON, generated image links, and errors
• Filters - all commands or specific commands such as /generate, /rewrite, /news, /whatsworking, /brand, /help, and /cancel
• Timing - created time and processing duration when available
• Chat and user IDs - identifiers for troubleshooting allowlist and access issues

Admin tools

Admins can:

• Cancel one processing command
• Cancel all in-flight commands for the org
• Clear errors
• Clear completed or canceled rows
• Clear all non-in-flight rows
• Unstick the Telegram webhook by dropping the pending-update backlog and re-registering the webhook

Use destructive cleanup actions carefully; cleared rows are removed from the bot log.

Workflow

• Open Bot History to audit a specific command or diagnose an error
• Use the active queue when the bot appears stuck
• Use admin recovery tools only when a command is truly stale or the webhook is replaying old updates

Security Log

Security Log now lives under Bot History. Open Bot History > Security Log to review sign-ins, role changes, settings updates, access events, and other security-sensitive activity.

Bot configuration - the health check and the chat/user allowlists - lives on the Settings tab of the same Telegram section (Settings > Telegram > Settings, admin-only).

Tips

• Bot History is an operational tool, not just a read-only archive
• Capture the timestamp, command, and error before escalating a recurring bot issue
• See Telegram Bot for setup and commands