Skip to content

Telegram DM stalls behind embedded auto-compaction session #83765

Closed as not planned
Closed as not planned
Telegram DM stalls behind embedded auto-compaction session#83765
Labels
P2Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
@ZULU-LABS

Description

@ZULU-LABS
ZULU-LABS
opened on May 18, 2026

OpenClaw Telegram DM stall report - 2026-05-18

Summary

Telegram DM ingress works, but a message appeared lost because the Telegram direct session was queued behind active work during embedded auto-compaction. The gateway later sent a response, but only after compaction/session takeover errors.

Timeline UTC

20:12:53 [telegram] Inbound message <telegram-user> -> <bot> (direct, 6 chars)
20:12:59 [agent/embedded] embedded run auto-compaction start: reason=overflow
20:14:34 [agent/embedded] embedded run auto-compaction complete: reason=overflow compactionCount=1 willRetry=true
20:15:00 [diagnostic] long-running session: sessionKey=agent:main:telegram:direct:<telegram-user> state=processing age=120s queueDepth=1 reason=queued_behind_active_work activeWorkKind=model_call
20:16:15 [agent/embedded] compaction retry aggregate timeout (60000ms): proceeding with pre-compaction state
20:16:15 [diagnostic] lane task error: lane=main error="EmbeddedAttemptSessionTakeoverError: session file changed while embedded prompt lock was released"
20:16:15 [diagnostic] lane task error: lane=session:agent:main:telegram:direct:<telegram-user> error="EmbeddedAttemptSessionTakeoverError: session file changed while embedded prompt lock was released"
20:16:19 [telegram] outbound send ok operation=sendVoice deliveryKind=voice

Expected developer review

  • Session queue should not make channel messages look silently dropped.
  • Telegram should send an interim queued/failure acknowledgement when the target session is blocked.
  • Embedded compaction/session takeover handling should recover cleanly for channel-originated turns.
  • Setup/config should not leave active placeholder entries like TU_TELEGRAM_ID_AQUI in Telegram allowlists.

GitHub attempt

Tried gh issue create --repo openclaw/openclaw; failed because the configured GitHub token lacks createIssue permission.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions