From e474130c487c5e4c3d58f309ec2fdb19474cc4dc Mon Sep 17 00:00:00 2001 From: AhmetArif0 <147827411+AhmetArif0@users.noreply.github.com> Date: Tue, 12 May 2026 18:45:57 -0700 Subject: [PATCH] fix(telegram): use thread fallback helper in slash-confirm result send PR #23458 introduced _send_message_with_thread_fallback() and applied it to all control-style sends (send_update_prompt, send_approval_request, send_model_picker_prompt), but the slash-confirm result message in handle_callback_query still called self._bot.send_message directly. In supergroups with stale message_thread_id on the callback's parent message, this raises "Message thread not found" and silently swallows the result text. Replace with the helper so the same retry-without- thread-id logic applies. --- gateway/platforms/telegram.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gateway/platforms/telegram.py b/gateway/platforms/telegram.py index 415ddb5608b..db25b87497d 100644 --- a/gateway/platforms/telegram.py +++ b/gateway/platforms/telegram.py @@ -2772,7 +2772,7 @@ class TelegramAdapter(BasePlatformAdapter): {"thread_id": str(thread_id)}, ) ) - await self._bot.send_message(**send_kwargs) + await self._send_message_with_thread_fallback(**send_kwargs) except Exception as exc: logger.error("[%s] slash-confirm callback failed: %s", self.name, exc, exc_info=True) return