From d343e5de99458181da904ba67003343ac68baa11 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sun, 3 May 2026 15:19:52 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@5b94c4ce9396b3b38e33be167ce564683736a0b8 --- .openclaw-sync/source.json | 4 ++-- docs/channels/telegram.md | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index a03f11ae6..20b53422d 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "0bf06e953fdda290799fc9fb9244a8f67fdae593", - "syncedAt": "2026-05-03T14:27:11.441Z" + "sha": "5b94c4ce9396b3b38e33be167ce564683736a0b8", + "syncedAt": "2026-05-03T15:17:52.790Z" } diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index 3030f91ef..a4f51e1b3 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -855,7 +855,8 @@ Per-account, per-group, and per-topic overrides are supported (same inheritance - `getMe returned 401` is a Telegram authentication failure for the configured bot token. - Re-copy or regenerate the bot token in BotFather, then update `channels.telegram.botToken`, `channels.telegram.tokenFile`, `channels.telegram.accounts..botToken`, or `TELEGRAM_BOT_TOKEN` for the default account. - `deleteWebhook 401 Unauthorized` during startup is also an auth failure; treating it as "no webhook exists" would only defer the same bad-token failure to later API calls. - - If `deleteWebhook` fails with a transient network error during polling startup, OpenClaw checks `getWebhookInfo`; when Telegram reports an empty webhook URL, polling continues because cleanup is already satisfied. + - If `deleteWebhook` fails with a transient network error during polling startup, OpenClaw continues into long polling instead of making another pre-poll control-plane call. A still-active webhook surfaces as a `getUpdates` conflict; OpenClaw then rebuilds the Telegram transport and retries webhook cleanup. + - After a successful startup `getMe` probe, OpenClaw reuses that bot identity for grammY polling startup so the runner does not need a second `getMe` before the first `getUpdates`.