Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram voice/audio messages have significant delivery delay (~2 minutes) before agent receives them [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#70517•Fetched 2026-04-24 05:57:03
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
LuisAmauryLuisAmaury
Participants
LuisAmauryLuisAmaury

When a Telegram user sends a voice message (OGG/Opus), the agent receives the message and processes the audio significantly later than when it was sent — observed delay of ~2 minutes. Text messages on the same channel are delivered and processed near-instantly.

Root Cause

When a Telegram user sends a voice message (OGG/Opus), the agent receives the message and processes the audio significantly later than when it was sent — observed delay of ~2 minutes. Text messages on the same channel are delivered and processed near-instantly.

RAW_BUFFERClick to expand / collapse

Bug type

Performance / Latency

Beta release blocker

No

Summary

When a Telegram user sends a voice message (OGG/Opus), the agent receives the message and processes the audio significantly later than when it was sent — observed delay of ~2 minutes. Text messages on the same channel are delivered and processed near-instantly.

Environment

  • OS: Ubuntu 24.04 (Linux 6.17.0-20-generic x64)
  • Node.js: v25.9.0
  • OpenClaw: 2026.4.22
  • Channel: Telegram (direct chat)

Steps to Reproduce

  1. Open a Telegram direct chat with the OpenClaw agent
  2. Send a text message → agent responds in seconds ✅
  3. Send a voice message (hold mic button) → agent responds ~2 minutes later ❌

Expected Behavior

Voice messages should be delivered and processed with similar latency to text messages (a few seconds at most, accounting for transcription time).

Actual Behavior

The agent receives and processes voice messages with a ~2 minute delay after the audio was sent. The transcription itself (local Parakeet TDT model) takes only ~1.5s, so the bottleneck appears to be in the Telegram media download/delivery pipeline within OpenClaw — not the STT processing.

Additional Context

  • Tested with multiple voice messages of varying lengths (5–35 seconds)
  • The audio file IS eventually delivered and transcribed correctly — it's purely a latency issue
  • Suspicion: Telegram media file download (via bot API) may be happening synchronously and blocking message delivery to the agent
  • Text messages containing the same content typed manually show no delay

extent analysis

TL;DR

The likely fix involves modifying the Telegram media download process in OpenClaw to handle voice messages asynchronously, preventing it from blocking message delivery to the agent.

Guidance

  • Investigate the Telegram bot API integration in OpenClaw to determine if the media file download is indeed happening synchronously, causing the delay.
  • Consider implementing asynchronous processing for voice message downloads to prevent blocking the agent's message delivery pipeline.
  • Review the OpenClaw documentation and source code to identify potential configuration options or code modifications that can enable asynchronous media downloads.
  • Test the hypothesis by simulating asynchronous downloads or using a different API endpoint that supports non-blocking downloads, if available.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The root cause is suspected to be related to the synchronous nature of the Telegram media download process, but further investigation is needed to confirm this. The provided information suggests that the transcription process itself is not the bottleneck.

Recommendation

Apply a workaround by modifying the OpenClaw configuration or code to enable asynchronous media downloads for voice messages, as this is likely to address the observed latency issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#latency issue#index setup#retrieval issue#search optimization

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Telegram voice/audio messages have significant delivery delay (~2 minutes) before agent receives them [1 participants]