Troubleshooting
The bot is silent, the menu never arrives, a setting seems ignored
Nearly every report falls into one of these. They are ordered by how often they turn out to be the answer.
The bot ignores everything
Send /isalive. If it answers, the bot can see and post in the group, and the
problem is narrower than "the bot is down".
If it does not answer:
- Is it actually in the group? Check the member list, not your memory of adding it.
- Is it an admin? Manage group → Administrators. Without rights it can still reply, but almost nothing else works.
- Was the command aimed at another bot?
/rules@some_other_botis deliberately ignored.
Commands work, but nothing automatic does
Sticker limits, link rewriting, the AI replies and anything else that reacts to ordinary messages need Telegram's privacy mode turned off for the bot. With privacy mode on — the default — a bot only receives messages addressed to it, so commands work and nothing else does. Only the bot's owner can change it, in BotFather.
Someone's sticker was deleted and they had only sent one
The sticker count is the group's, not each member's: one person can push the group past Stickers limit and the next person's sticker is the one deleted. Admins are not exempt either. Both are v1 behaviours, kept deliberately — raise the limit if the group is chatty in stickers.
The bot stopped answering one person
The conversational replies cap at seven consecutive triggers from the same member: six answers, then silence. Ordinary messages replenish it. Nothing is wrong, and nothing needs resetting.
If it is not answering anyone, check Fun Functions — with it off the AI replies go quiet rather than announcing that they are disabled.
A typo turned into a picture search
That is the catch-all: any command the bot does not recognise becomes a Google
Images search. /isalive and every other real command are never hijacked, and a
command carrying a link searches nothing. Turn Utility Functions off to stop
it entirely — see AI features.
/birthday asks me to type a name
It wants an argument: /birthday @someone. A bare /birthday never looks
anything up — v1 behaviour, kept. The unprompted daily post at 00:10 UTC is the
one that finds today's birthdays by itself.
/config says it messaged me and nothing arrived
Telegram forbids a bot from opening a private chat. Open a private chat with
the bot and press Start, then run /config again.
If you are posting as an anonymous admin, Telegram gives the bot no account to message at all — turn anonymity off for that one command.
A setting does not stick
The menu opens for whoever it is shown to, but a value is only accepted from an
admin. If a numeric field keeps asking again, the reply was not a number: the
bot answers ERROR: invalid input — try again and stores nothing until a value
parses.
Changes apply immediately once accepted. There is no cache to wait out and no
/reload to send.
New members are being removed
That is the captcha doing its job — but check the timer. 🕒 CAPTCHA defaults
to 120 seconds, which is short for a group where people arrive, get distracted,
and come back. Raise it to 300, or set 0 to turn screening off.
Removal is temporary: the block lifts shortly after, so a real person can rejoin and try again.
New members cannot post images
That is 🕒 Limbo, the media hold. The bot says how long it lasts when it
greets them. Set it to 0 to turn it off.
Nothing happened when I set the rules
/newrules and /newwelcome are two-step. The bot posts a prompt and you must
reply to that prompt — typing the text on the same line as the command does
nothing at all. Only an admin's reply is accepted; a non-admin gets
You are not a group admin!.
Still stuck
Check the progress board: a command that has not moved to the new stack yet behaves the way the current release behaves, and a feature marked partial does part of what its page describes.
Then tell us. Nobody working on the bot can see your group, so a report of what actually happened there is information only you have — and it is the most useful thing this project gets.
Something is broken
A command or a moderation feature doing the wrong thing.
It used to behave differently
A command that changed its wording, its permissions or its reply.
An idea
A better default, a missing command, a rough edge. Half-formed is fine.
These docs are wrong
A page that says something untrue, or a question it should have answered.
/analysis, sent as a reply to the message that misbehaved, dumps exactly
what the bot received — pasting that into an issue is worth a paragraph of
description. Strip anything private first; it is a raw Telegram payload. And
never report a security problem in a public issue: use
a private advisory.