openclaw - 💡(How to fix) Fix [Bug] Telegram messages delivered multiple times (duplicate message_id injection) [1 participants]

TL;DR

Implementing message deduplication based on message_id in the Telegram message processing pipeline is likely to fix the issue of duplicate messages being delivered to agent sessions.

Guidance

• Investigate the Telegram message processing pipeline to identify where duplicates are being introduced, focusing on the handling of message_id.
• Verify that the message_id is correctly being passed and logged in the session .jsonl files to ensure consistency.
• Consider implementing a cache or set to keep track of recently processed message_ids to filter out duplicates before injecting messages into the session.
• Review the OpenClaw 2026.4.23 documentation to see if there are any built-in mechanisms for handling message deduplication that can be leveraged.

Example

No specific code example can be provided without more details on the implementation, but a simple deduplication mechanism might involve checking a set of recently seen message_ids before processing a new message.

Notes

The solution may require modifications to the existing message processing pipeline and could potentially involve updating the OpenClaw version if a fix is available in a later release. However, without more specific information about the pipeline's implementation, it's difficult to provide a precise fix.

Recommendation

Apply a workaround by implementing message deduplication based on message_id in the Telegram message processing pipeline, as this directly addresses the observed issue of duplicate messages being delivered to agent sessions.