Bot is not responding
Check the basics first: the bot is still reachable in Telegram, the hosting service is live, the bot is not sleeping or restarting, and the deployment environment still has valid secrets configured.
Webhook and hosting notes
If the bot is hosted as a webhook-based service, publishing and command handling depend on the public webhook URL, a healthy running web service, and a valid Telegram webhook configuration.
No admin rights
If the bot cannot publish, verify it is in the channel, verify it is an admin, and verify it has posting rights. This is one of the most common setup failures.
Invalid Groq key
If the connected Groq key is invalid, /post will fail and generation cannot proceed. Reconnect the key through /ai if needed.
No channel metadata in forwarded posts
Some forwarded posts do not expose enough channel information. When that happens, forward another post or use the channel ID manually.
Caption too long
Telegram captions have limits. If a post with a photo is too long, the bot may need to shorten or adapt the result so the media and text can still be published in a usable way.
Photo issues
If the photo is weak or off-topic, refresh the photo or upload your own image. Do not treat automatic visual selection as final editorial output.
Payment issues
If access does not look correct after payment, check the in-bot status flow, wait a moment for the payment event to settle, and contact support if the issue persists.
