Expired50% confidenceFactTime unknown
The Telegram message queue congestion issue has been fixed in v2026.5.14 by isolating polling threads so each message type has its own independent processing pipeline
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
7/2/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 9/30/2026(expired)
Sources
OpenClaw v2026.5.14 Deep Dive: Real-Time Voice Calls and Gateway Freeze Fix
bilibilibig叔大
Related Claims
UnverifiedTelegram message queue congestion was caused by multiple polling threads not being properly isolated, causing messages from group topics, private DMs, and status control commands to block each other in the same queue84% similarUnverifiedThe Telegram Bot API uses a Long Polling mechanism to fetch message updates67% similarUnverifiedThe project has a built-in Telegram Bot that can receive new email notifications and view their content via Telegram.54% similarUnverifiedSending messages with a Slack Bot requires the chat:write permission, and listening to channel messages requires subscribing to the message.channels event.53% similarUnverifiedTelegram 默认的云端消息不启用 E2EE，仅其秘密聊天功能采用端对端加密50% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/56299API
curl https://kongchang.com/api/v1/knowledge/claims/56299MCP
get_claim(id=56299)