Telegram 私聊禁发 `message_thread_id` 排错方案（PR #14821）

解决“Cron/自动回复在私聊报 `message thread not found`”的场景：DM scope 下省略线程参数。

GITHUBDiscovered 2026-02-13Author superlowburn

Prerequisites

Telegram channel is enabled and at least one delivery path targets private chats.
You can test both DM and forum-topic group deliveries.

Steps

Collect failing logs and confirm signature `400: Bad Request: message thread not found` on DM target.
Upgrade to PR #14821 build and restart gateway.
Replay one DM send (manual or cron) and verify outgoing payload omits `message_thread_id`.
Run regression test on forum-topic groups to ensure thread-id still works where supported.
Document routing rules: DM vs group/forum scope normalization.

Commands

openclaw gateway status

openclaw gateway restart

openclaw status

openclaw cron run --job <jobId>

Verify

DM deliveries succeed without thread errors, while topic-enabled groups keep correct threaded delivery.

Caveats

Mixed relay/proxy integrations may transform chat scope labels (`dm`/`direct`) differently（需验证）.
Legacy jobs with hardcoded thread fields should be reviewed manually.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.