From 0d1a59a93db7e52a198482a2c758ffdfc679d668 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Wed, 29 Apr 2026 14:43:40 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@204ef7f1c45b5377fe272b068fdec15e32789247 --- .openclaw-sync/source.json | 4 ++-- docs/channels/telegram.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index a1bf33eea..b20fca5e8 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "71084140090f9ace1ab587a076d4a3d8f81ac1c8", - "syncedAt": "2026-04-29T14:40:59.313Z" + "sha": "204ef7f1c45b5377fe272b068fdec15e32789247", + "syncedAt": "2026-04-29T14:42:03.374Z" } diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index 5419a1ac2..76849fe7a 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -867,7 +867,7 @@ Per-account, per-group, and per-topic overrides are supported (same inheritance - Some hosts resolve `api.telegram.org` to IPv6 first; broken IPv6 egress can cause intermittent Telegram API failures. - If logs include `TypeError: fetch failed` or `Network request for 'getUpdates' failed!`, OpenClaw now retries these as recoverable network errors. - If logs include `Polling stall detected`, OpenClaw restarts polling and rebuilds the Telegram transport after 120 seconds without completed long-poll liveness by default. - - `openclaw channels status --probe` and `openclaw doctor` warn when a running polling account has not completed `getUpdates` after startup grace, or when its last successful polling transport activity is stale. + - `openclaw channels status --probe` and `openclaw doctor` warn when a running polling account has not completed `getUpdates` after startup grace, when a running webhook account has not completed `setWebhook` after startup grace, or when the last successful polling transport activity is stale. - Increase `channels.telegram.pollingStallThresholdMs` only when long-running `getUpdates` calls are healthy but your host still reports false polling-stall restarts. Persistent stalls usually point to proxy, DNS, IPv6, or TLS egress issues between the host and `api.telegram.org`. - Telegram also honors process proxy env for Bot API transport, including `HTTP_PROXY`, `HTTPS_PROXY`, `ALL_PROXY`, and their lowercase variants. `NO_PROXY` / `no_proxy` can still bypass `api.telegram.org`. - If the OpenClaw managed proxy is configured through `OPENCLAW_PROXY_URL` for a service environment and no standard proxy env is present, Telegram uses that URL for Bot API transport too.