mirror of
https://github.com/openclaw/openclaw.git
synced 2026-07-16 09:36:26 +02:00
d94de5c4a1
* fix(cron): pass job.delivery.accountId through to delivery target resolution * fix(cron): normalize topic-qualified target.to in messaging tool suppress check When a cron job targets a Telegram forum topic (e.g. delivery.to = "-1003597428309:topic:462"), delivery.to is stripped to the chatId only by resolveOutboundTarget. However, the agent's message tool may pass the full topic-qualified address as its target, causing matchesMessagingToolDeliveryTarget to fail the equality check and not suppress the tool send. Strip the :topic:NNN suffix from target.to before comparing so the suppress check works correctly for topic-bound cron deliveries. Without this, the agent's message tool fires separately using the announce session's accountId (often "default"), hitting 403 when default bot is not in the multi-account target group. * fix(cron): remove duplicate accountId keys after rebase --------- Co-authored-by: jaxpkm <jaxpkm@jaxpkmdeMac-mini.local> Co-authored-by: Tak Hoffman <781889+Takhoffman@users.noreply.github.com>