openclaw - 💡(How to fix) Fix [Bug]: message tool fails sending to Telegram forum topics (announce fallback works)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

When a cron job agent tries to use the message tool to send to a Telegram forum topic, the tool call fails with:

⚠️ ✉️ Message: `4` failed

However, the system-level announce delivery to the same topic succeeds every time (via fallback). This suggests the message tool has a routing/parameter issue with forum topic targets that the announce path does not.

Error Message

| 2026-05-12 00:30 | error | FAIL Message: 4 failed | OK delivered (fallback) | | 2026-05-11 00:30 | error | FAIL Message: 4 failed | OK delivered (fallback) | | 2026-05-09 00:30 | error | FAIL Message: 4 failed | OK delivered (fallback) | {"ts": 1778538993776, "source": "tool", "severity": "error", "message": "⚠️ ✉️ Message: 4 failed"}, {"ts": 1778538995181, "source": "agent-run", "severity": "error", "message": "⚠️ ✉️ Message: 4 failed"}

Root Cause

When a cron job agent tries to use the message tool to send to a Telegram forum topic, the tool call fails with:

⚠️ ✉️ Message: `4` failed

However, the system-level announce delivery to the same topic succeeds every time (via fallback). This suggests the message tool has a routing/parameter issue with forum topic targets that the announce path does not.

Fix Action

Workaround

Relying on delivery.mode = "announce" with fallbackUsed: true — this works reliably but means the message tool is unreliable for programmatic sends from within agent runs.

Code Example

⚠️ ✉️ Message: `4` failed

---

{
  "diagnostics": {
    "summary": "⚠️ ✉️ Message: `4` failed",
    "entries": [
      {"ts": 1778538993776, "source": "tool", "severity": "error", "message": "⚠️ ✉️ Message: `4` failed"},
      {"ts": 1778538995181, "source": "agent-run", "severity": "error", "message": "⚠️ ✉️ Message: `4` failed"}
    ]
  },
  "delivery": {
    "intended": {"channel": "telegram", "to": "-1003707963225:4", "source": "explicit"},
    "resolved": {"ok": true, "channel": "telegram", "to": "-1003707963225", "threadId": 4, "source": "explicit"},
    "fallbackUsed": true,
    "delivered": true
  }
}
RAW_BUFFERClick to expand / collapse

Bug: Telegram message tool fails sending to forum topic, announce delivery works as fallback

OpenClaw version: 2026.5.3 Channel: Telegram (forum/group with topics)

Description

When a cron job agent tries to use the message tool to send to a Telegram forum topic, the tool call fails with:

⚠️ ✉️ Message: `4` failed

However, the system-level announce delivery to the same topic succeeds every time (via fallback). This suggests the message tool has a routing/parameter issue with forum topic targets that the announce path does not.

Reproduction

  1. Create an isolated cron job with delivery.mode = "announce" targeting a Telegram forum topic (e.g., to: "-1003707963225", threadId: "4")
  2. In the cron prompt, instruct the agent to use the message tool: action=send, channel=telegram, target=-1003707963225, threadId=4
  3. The agent generates the content successfully
  4. The message tool call fails with ⚠️ ✉️ Message: '4' failed
  5. The announce fallback delivers the message correctly to the topic

Evidence from run history

Cron job: "Morning Brief" (5c5d818b) Target: Telegram group -1003707963225, topic 4

Recent runs showing the pattern:

Run time (UTC)Statusmessage toolannounce delivery
2026-05-12 00:30errorFAIL Message: 4 failedOK delivered (fallback)
2026-05-11 00:30errorFAIL Message: 4 failedOK delivered (fallback)
2026-05-10 00:30okFAIL (diagnostic)OK delivered (fallback)
2026-05-09 00:30errorFAIL Message: 4 failedOK delivered (fallback)

This pattern repeats consistently. The agent always generates valid content, the message tool always fails, and announce always rescues it.

The same pattern affects multiple cron jobs targeting different topics (2, 4, 19, 20). Topic 20 (TikTok DB Sync) has the same Message: 20 failed pattern.

Diagnostic details from a failed run

{
  "diagnostics": {
    "summary": "⚠️ ✉️ Message: `4` failed",
    "entries": [
      {"ts": 1778538993776, "source": "tool", "severity": "error", "message": "⚠️ ✉️ Message: `4` failed"},
      {"ts": 1778538995181, "source": "agent-run", "severity": "error", "message": "⚠️ ✉️ Message: `4` failed"}
    ]
  },
  "delivery": {
    "intended": {"channel": "telegram", "to": "-1003707963225:4", "source": "explicit"},
    "resolved": {"ok": true, "channel": "telegram", "to": "-1003707963225", "threadId": 4, "source": "explicit"},
    "fallbackUsed": true,
    "delivered": true
  }
}

Expected behavior

The message tool should successfully send to forum topics when provided with target (group chat ID) and threadId (topic ID).

Workaround

Relying on delivery.mode = "announce" with fallbackUsed: true — this works reliably but means the message tool is unreliable for programmatic sends from within agent runs.

Related

  • #76554 (fixed in 5.3 for final reply delivery, but message tool itself still fails for forum topics)

Environment

  • Telegram forum group: -1003707963225
  • Topics tested: 2, 4, 19, 20
  • OpenClaw: 2026.5.3
  • Agent runtime: isolated cron sessions

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The message tool should successfully send to forum topics when provided with target (group chat ID) and threadId (topic ID).

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: message tool fails sending to Telegram forum topics (announce fallback works)