fix(telegram): verify final stream edit landed · openclaw...
obviyus
·
2026-05-06
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -343,10 +343,9 @@ curl "https://api.telegram.org/bot<bot_token>/getUpdates"
|
343 | 343 | |
344 | 344 | For text-only replies: |
345 | 345 | |
346 | | -- short DM/group/topic previews: OpenClaw keeps the same preview message and performs a final edit in place, unless a visible non-preview message was sent after the preview appeared |
| 346 | +- short DM/group/topic previews: OpenClaw keeps the same preview message and performs the final edit in place |
347 | 347 | - long text finals that split into multiple Telegram messages reuse the existing preview as the first final chunk when possible, then send only the remaining chunks |
348 | | -- previews followed by visible non-preview output: OpenClaw sends the completed reply as a fresh final message and cleans up the older preview, so the final answer appears after intermediate output |
349 | | -- previews older than about one minute: OpenClaw sends the completed reply as a fresh final message and then cleans up the preview, so Telegram's visible timestamp reflects completion time instead of the preview creation time |
| 348 | +- if the final edit fails before the completed text is confirmed, OpenClaw uses normal final delivery and cleans up the stale preview |
350 | 349 | |
351 | 350 | For complex replies (for example media payloads), OpenClaw falls back to normal final delivery and then cleans up the preview message. |
352 | 351 | |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
