Skip to content

[Bug] Telegram: duplicate message delivery — same response sent twice #37697

@mj-deving

Description

@mj-deving

Description

Every assistant response is delivered twice to Telegram. The session log shows a single outbound message, so the duplication is happening in the delivery layer, not in the agent.

Steps to Reproduce

  1. Run any agent session over Telegram (direct chat)
  2. Send a message and receive a response
  3. The same response appears twice in Telegram

Expected Behavior

Each assistant response is delivered once.

Actual Behavior

Each assistant response is delivered twice (exact duplicate, back-to-back).

Environment

  • Channel: Telegram
  • Agent: main session (direct chat)
  • OpenClaw version: v2026.2.24

Additional Context

  • Verified the session JSONL log — only one assistant message entry per turn
  • The agent is not using the message tool (which could cause double-send if NO_REPLY is missed)
  • Duplication is consistent, not intermittent
  • Delivery queue at ~/.openclaw/delivery-queue/ shows no relevant retries for these messages

This points to the Telegram outbound dispatch layer sending the message twice, possibly a retry on an ACK timeout that doesn't check for prior successful delivery.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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