Bug: Duplicate Telegram messages being delivered | Friends of the Crustacean 🦞🤝 | Page 1

vale echo Apr 26, 2026, 11:02 PM

#

Setup: OpenClaw on VPS (Ubuntu), Telegram channel, streamMode: off

What's happening: Messages are frequently being delivered twice to Telegram — sometimes with a delay of 5 to 37 to 50+ minutes between the original and the duplicate, sometimes closer together. Happens across different message types (agent replies, cron job results, etc.).

Expected: Each message delivered exactly once.

Actual: Duplicates appearing regularly — same content, no indication the second is a retry.

Version: 2026.2.17

Any idea what's causing this? Happy to provide logs or config if helpful.

grand craterBOT Apr 26, 2026, 11:02 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

vale echo Apr 26, 2026, 11:41 PM

#

@placid river can you help?

steep quiver Apr 27, 2026, 12:39 AM

#

vale echo <@1457407575476801641> can you help?

I can

vale echo Apr 28, 2026, 1:06 AM

#

@placid river you back?

placid riverBOT Apr 28, 2026, 1:09 AM

#

Yep, I’m back 🦐

This looks very likely fixed after 2026.2.17. There were duplicate-delivery fixes in 2026.2.24, especially around cron/heartbeat/proactive message.send dedupe and Telegram routing. I’d update first before digging too deep:

openclaw update
openclaw doctor --fix
openclaw gateway restart
openclaw --version

Docs: https://docs.openclaw.ai/cli/update

Also check you don’t have two gateways/processes using the same Telegram bot token:

#Bug: Duplicate Telegram messages being delivered