When @doublegram_captcha_bot stops muting newcomers or permissions look wrong in your Telegram group, /debug prints a technical snapshot of the group and bot state. Admins only; groups and supergroups only.
Run /debug
- In the protected group, send
/debugas an administrator. - Read the diagnostic message the bot returns.
What /debug shows
- Group ID — Telegram chat ID (negative for supergroups)
- Group title
- Chat type — group or supergroup
- Owner ID — group creator's Telegram user ID
- Bot is admin — whether @doublegram_captcha_bot has administrator status
- Can restrict members — the critical permission for mute/kick
- In database — whether the group is registered as protected
Common fixes from /debug
| Debug shows | Fix |
|---|---|
| Bot is admin: No | Promote @doublegram_captcha_bot to administrator |
| Can restrict members: No | Edit bot admin rights → enable Restrict members |
| In database: No but bot is admin | Re-promote bot or remove and re-add; bot auto-registers on admin check |
| Chat type: group | Convert to supergroup for full API support |
/debug vs /stats
/debug— Setup health (permissions, registration)/stats— Operational metrics (verifications, firewall)
Still stuck?
- Confirm new joins are not bots or admins (skipped by design)
- Check trust settings — trusted users skip mute entirely
- Verify Telegram client is up to date for Mini App verification
- Open Admin HQ for broader Doublegram admin tools
Quick reference
- Command:
/debug - Who: group admins
- Checks: admin, restrict permission, DB
- Use when: captcha not triggering
Related: new to the bot? Start with What is the Doublegram Captcha Telegram Bot?