ripe gulch
Hi — running on myclaw.ai cloud (not self-hosted). Configured Telegram with a valid bot token. openclaw status shows Telegram: ON / OK and getMe returns fine, but the channel is never polling — pending_update_count keeps growing at Telegram's side and messages are never consumed.
What I see:
Gateway restarts cleanly after config changes (channels.telegram requires restart, confirmed in logs)
After restart, zero Telegram-specific runtime logs — no polling start, no getUpdates, no errors
openclaw pairing list telegram works (returned "no pending requests") but actual messages from Telegram never arrive
getWebhookInfo shows no webhook set, pending count grows with every message sent
Config:
Copy
channels: {
telegram: {
enabled: true,
botToken: "...",
dmPolicy: "allowlist",
allowFrom: ["telegram:<my-user-id>"],
streaming: { mode: "partial" },
replyToMode: "first"
}
}
Question: Is there something specific needed to get Telegram long-polling working on the myclaw.ai cloud platform? Does the gateway process have outbound access to api.telegram.org? Or is webhook mode required for cloud deployments?
OpenClaw version: 2026.5.2