Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram isolated ingress drain can hang after offset advances

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…

Root Cause

Observed on local install:

  • isolated Telegram worker wrote telegram/ingress-spool-default/0000000379952079.json
  • update-offset-default.json advanced to lastUpdateId=379952079
  • main gateway did not dispatch the spooled update into the session
  • Telegram would not redeliver because offset was already advanced
  • spool drain path awaited bot.handleUpdate(update.update) without a timeout/liveness watchdog, so drainActive could stay true indefinitely and future drain ticks no-op

Fix Action

Fix / Workaround

Observed on local install:

  • isolated Telegram worker wrote telegram/ingress-spool-default/0000000379952079.json
  • update-offset-default.json advanced to lastUpdateId=379952079
  • main gateway did not dispatch the spooled update into the session
  • Telegram would not redeliver because offset was already advanced
  • spool drain path awaited bot.handleUpdate(update.update) without a timeout/liveness watchdog, so drainActive could stay true indefinitely and future drain ticks no-op

Local mitigation applied to installed runtime:

  • added deadline around spooled bot.handleUpdate
  • added stuck-drain diagnostics
  • restarted gateway; stuck spool drained and inbound Telegram resumed

The durable fix should address isolated ingress offset/dispatch semantics and add watchdog/stale-spool diagnostics in source.

RAW_BUFFERClick to expand / collapse

OpenClaw 2026.5.12 isolated Telegram ingress can wedge inbound delivery while the poller still appears healthy.

Observed on local install:

  • isolated Telegram worker wrote telegram/ingress-spool-default/0000000379952079.json
  • update-offset-default.json advanced to lastUpdateId=379952079
  • main gateway did not dispatch the spooled update into the session
  • Telegram would not redeliver because offset was already advanced
  • spool drain path awaited bot.handleUpdate(update.update) without a timeout/liveness watchdog, so drainActive could stay true indefinitely and future drain ticks no-op

Local mitigation applied to installed runtime:

  • added deadline around spooled bot.handleUpdate
  • added stuck-drain diagnostics
  • restarted gateway; stuck spool drained and inbound Telegram resumed

The durable fix should address isolated ingress offset/dispatch semantics and add watchdog/stale-spool diagnostics in source.

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…
#environment setup#docker error#permission error#memory optimization#batch processing

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 Telegram isolated ingress drain can hang after offset advances