Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram group topic delivery broken in 2026.4.27 - replies sent to DM instead of topic [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75238•Fetched 2026-05-01 05:36:24
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Author
Felox63Felox63
Participants
clawsweeper[bot]clawsweeper[bot]Felox63Felox63
Timeline (top)
closed ×1commented ×1mentioned ×1subscribed ×1

Error Message

  • No error messages in gateway logs related to delivery failures

Fix Action

Fix / Workaround

  • OpenClaw version: 2026.4.27 (downgraded to 2026.4.26 as workaround)
  • Channel: Telegram (forum topics enabled)
  • Config: Group ID -xxxxxxxxxx, Topic ID xx, agent ID xxxx
  • Delivery config: requireMention: false, groupPolicy: "allowlist"
  • Gateway mode: local, port 18789
RAW_BUFFERClick to expand / collapse

Describe the bug

After upgrading to 2026.4.27, assistant replies in Telegram group topics are not delivered to the correct chat destination. Instead of being sent to the group topic (with correct chat_id and message_thread_id), replies silently fail — they are neither delivered as DM nor as topic message.

Downgrading to 2026.4.26 resolves the issue.

To Reproduce

  1. Configure a Telegram group with a forum topic (topic ID 2) mapped to an agent
  2. Send a message in the topic
  3. Observe: assistant reply never appears in the topic

Expected behavior

Assistant replies should be delivered to the originating Telegram group topic with the correct message_thread_id.

Actual behavior

  • No sendMessage calls appear in the gateway logs (log file shows 0 entries containing "sendMessage" after upgrade)
  • Gateway logs show no errors related to delivery
  • Replies are generated successfully (visible in session history via dashboard) but never reach Telegram
  • All agents (xxxxxx, xxxxx, xxxxxx) running in the same OpenClaw instance are affected for group topics

Environment

  • OpenClaw version: 2026.4.27 (downgraded to 2026.4.26 as workaround)
  • Channel: Telegram (forum topics enabled)
  • Config: Group ID -xxxxxxxxxx, Topic ID xx, agent ID xxxx
  • Delivery config: requireMention: false, groupPolicy: "allowlist"
  • Gateway mode: local, port 18789

Additional context

  • The sendMessage log entries that were observable in 2026.4.26 are completely absent in 2026.4.27
  • Session delivery context (sessions.json) is correctly populated with chatId, threadId, lastTo
  • No error messages in gateway logs related to delivery failures
  • Issue affects all agents (neo, md, codee) with telegram group topic routing
  • Changelog of 2026.4.27 includes changes to channel routing, target resolution, and Telegram approval routing — one of these likely introduced the regression

Suspected regression

The following changelog entries from 2026.4.27 are likely related:

  • Plugin SDK: expose shared channel route normalization, parser-driven target resolution (potential delivery target mismatch)
  • Channels/Telegram: honor multi-bot approval routing (potential side effect on regular delivery)
  • Various channel-route and target-resolution changes in Plugin SDK

extent analysis

TL;DR

Downgrade to version 2026.4.26 as a temporary workaround to resolve the issue with assistant replies not being delivered to the correct Telegram group topic.

Guidance

  • Review the changelog entries for 2026.4.27, specifically the changes to channel routing, target resolution, and Telegram approval routing, to identify the potential cause of the regression.
  • Verify that the sessions.json file is correctly populated with chatId, threadId, and lastTo to ensure that the session delivery context is set up correctly.
  • Investigate the Plugin SDK changes, particularly the exposure of shared channel route normalization and parser-driven target resolution, to determine if they are causing a delivery target mismatch.
  • Check the gateway logs for any errors or warnings related to channel routing or target resolution that may indicate the root cause of the issue.

Example

No code snippet is provided as the issue is related to a specific version regression and requires further investigation into the changelog entries and Plugin SDK changes.

Notes

The issue seems to be specific to version 2026.4.27, and downgrading to 2026.4.26 resolves the issue. However, this is only a temporary workaround, and the root cause needs to be identified and fixed.

Recommendation

Apply the workaround by downgrading to version 2026.4.26 until the root cause of the regression is identified and fixed, as it is the only known solution at this time.

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

Assistant replies should be delivered to the originating Telegram group topic with the correct message_thread_id.

#callback error#memory management#API rate limit#retriever error#indexing error

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 Telegram group topic delivery broken in 2026.4.27 - replies sent to DM instead of topic [1 comments, 2 participants]