Sending the same message in a loop

[winter linden]

This has happed several times this last few days. The agent might be doing good work, but it keeps sending the same message on Telegram. And it seems to have a delayed reaction.

I'm on Mac using Qwen3.6 Plus

[wise pelican]

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

[brisk arch]

Yeah, this sounds more like a Telegram delivery/streaming bug than Qwen deciding to spam.

A couple of concrete checks:

1. What does openclaw --version print?
2. In ~/.openclaw/openclaw.json, check channels.telegram.streaming.

If it is "partial" or "progress", I’d switch it to "off" first:

{
  channels: {
    telegram: {
      streaming: "off",
    },
  },

}

Then restart the gateway.

Why I’m pointing there: Telegram has had a few duplicate-message bugs around partial streaming / preview edits, and the current docs explicitly show streaming: "off" as the safer default for Telegram now.

Also worth checking:

• if you enabled block streaming, turn that off too:
  agents.defaults.blockStreamingDefault: "off"

If you’re on an older version, I’d upgrade first. There were Telegram duplicate-reply fixes in newer releases, including DM dedupe work in 2026.3.8+.

Docs:

• https://docs.openclaw.ai/channels/telegram
• https://docs.openclaw.ai/concepts/streaming

If you paste:

• openclaw --version
• your channels.telegram block
• whether the duplicate is brief flicker vs permanently repeated messages

…I can narrow it down pretty fast.

[winter linden]

cool

[brisk arch]

👍 Sounds good.

Paste openclaw --version and your channels.telegram block when you have it, and I’ll help narrow it down.

[winter linden]

❯ openclaw --version
OpenClaw 2026.4.14 (323493f)

"channels": {
"telegram": {
"enabled": true,
"groups": {
"*": {
"requireMention": true
}
},
"botToken": "<--redracted-->"
}
},

[brisk arch]

Nice, that helps.

You’re on a current version, and your pasted Telegram config does not show streaming, so this probably is not the older streaming: "partial" duplicate bug.

That makes me lean more toward a Telegram delivery/routing regression than a Qwen config mistake.

Two useful questions:

1. Does the duplicate show up only in Telegram, or also in the Control UI / TUI transcript?
2. Is this happening in a Telegram DM or a group/topic?

And the next checks from the troubleshooting docs are:

openclaw status
openclaw channels status --probe
openclaw logs --follow

Then trigger one duplicated reply and paste the relevant log lines.

What I’m looking for:

• Telegram-only duplicate, single transcript reply → channel delivery bug
• Exact same message re-sent later → possible stuck session / retry loop

Docs:

• https://docs.openclaw.ai/channels/troubleshooting
• https://docs.openclaw.ai/channels/telegram

If the logs confirm Telegram double-delivery on 2026.4.14, I’d file it here: https://github.com/openclaw/openclaw/issues

[winter linden]

Found it

It was a retry loop where each failed cargo check triggered the same response pattern without making actual progress

You can close this

[brisk arch]

Ah, yep, that makes sense.

So the Telegram spam was a symptom, not the root cause. The real problem was the agent getting stuck in a retry loop on the same failing cargo check, then re-sending the same kind of status reply each time.

Good catch 👍

To avoid this next time, I’d make the agent bail out after 1 or 2 identical failures and report the error instead of retrying blindly.

Glad that helped! 🎉
If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution.
This helps Answer Overflow index the solution for future users.

I can’t archive/close the Discord thread from here, but this looks resolved.

If you haven’t already, please mark the solution first, then you can archive the thread.

[winter linden]

I only have mark unread