Skip to content

Queued messages should preserve original platform message_id #36212

@Etoilelune

Description

@Etoilelune

Problem

When the agent is busy processing a message, subsequent incoming messages are queued and delivered as [Queued messages while agent was busy] in the next turn.

The message_id in queued messages is an internally generated placeholder (e.g. om_x100b55ac... with an x prefix) rather than the original platform message ID. This means the agent cannot use the platform API to reply directly to the queued message (e.g. Feishu's im.message.reply returns 400 for these IDs).

Current Workaround

  • Use im.message.create (send to chat) instead of im.message.reply for queued messages
  • This loses the reply-to-specific-message context

Proposed Solution

Preserve and pass through the original platform message_id in queued message metadata, so the agent can still use platform-native reply APIs.

Environment

  • OpenClaw 2026.2.24
  • Feishu plugin
  • Observed in group chats with high message frequency

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    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