A channel went offline
Channels can go offline if a token is revoked, rate-limited, or the bot is removed. Self-serve fix path.
What this is
Messages to your bot aren't getting replies, and Beach Settings shows the channel as offline or disconnected. A channel "going offline" almost always means something changed on the channel side — for example, the Telegram bot token was revoked, or you removed the bot from a chat. Beach can't fix that for you; you fix it at the source and re-paste the new credentials into Beach.
Try these in order
- Open Beach Settings → Channels and check the channel's status. If it shows an error message, note what it says — that often points directly at the fix.
- Check whether the token was revoked at the source. This is the most common cause. For Telegram: if you regenerated the bot token in @BotFather (deliberately or by accident), the old one stops working immediately. Generate a fresh token at the source, then re-paste it in Beach Settings → Channels.
- Wait it out if you're rate-limited. If the channel side is rate-limiting your bot (usually after a burst of activity), Beach will reconnect on its own once the limit clears. A few minutes is typical.
- Re-add the bot if it was removed from a chat. On Telegram, if you removed your bot from the conversation, just re-add it — no token change needed.
- Reconnect from scratch as a last resort. Disconnect the channel in Beach Settings, then run the channel setup wizard again with fresh credentials.
Note on the boundary
Channels are connections between your OpenClaw agent and a third-party messaging platform. Beach stores the credentials securely and hands them to OpenClaw — but the health of the connection depends on the platform (Telegram, etc.) accepting your token. If the platform rejects it, no setting in Beach will fix it. You have to fix it on their side first.
Related
Still stuck?
Contact support — see Getting support.