From 54eaeac4766cfa324a879dc253481932d13e46ce Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Wed, 29 Apr 2026 12:01:30 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@4f540c703ff65fc52908be06bb56dd7290653bee --- .openclaw-sync/source.json | 4 ++-- docs/channels/telegram.md | 1 + docs/zh-CN/concepts/active-memory.md | 1 + 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index c2ebcaad1..2ffaabe9f 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "1fb58ca5eee0f4f38343165b01204bd81bc2c1a5", - "syncedAt": "2026-04-29T11:43:42.544Z" + "sha": "4f540c703ff65fc52908be06bb56dd7290653bee", + "syncedAt": "2026-04-29T11:59:52.058Z" } diff --git a/docs/channels/telegram.md b/docs/channels/telegram.md index 9ab130b2f..f9d421f3b 100644 --- a/docs/channels/telegram.md +++ b/docs/channels/telegram.md @@ -867,6 +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. - 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. diff --git a/docs/zh-CN/concepts/active-memory.md b/docs/zh-CN/concepts/active-memory.md index 09eefacdf..a49128b9e 100644 --- a/docs/zh-CN/concepts/active-memory.md +++ b/docs/zh-CN/concepts/active-memory.md @@ -608,6 +608,7 @@ plugins.entries.active-memory - 查看 Gateway 网关日志中的 `active-memory: ... start|done`、`memory sync failed (search-bootstrap)` 或提供商嵌入错误。 - 运行 `openclaw memory status --deep`，检查 memory-search 后端和索引健康状况。 - 如果你使用 `ollama`，请确认已安装嵌入模型（`ollama list`）。 +