fix(telegram): preserve messageThreadId for DM reply threads
Previously, resolvedThreadId was always used for delivery, but resolveTelegramForumThreadId() returns undefined for non-forum chats. This caused DM reply threads to lose their thread context, sending replies to the main chat instead of the thread. Now we use messageThreadId directly for DM chats, while keeping resolvedThreadId for forum groups where topic resolution is needed.
This commit is contained in:
parent
6372242da7
commit
6a100e38d4
@ -656,7 +656,8 @@ export const buildTelegramMessageContext = async ({
|
||||
msg,
|
||||
chatId,
|
||||
isGroup,
|
||||
resolvedThreadId,
|
||||
// For DM reply threads use messageThreadId; for forum groups use resolvedThreadId
|
||||
resolvedThreadId: isGroup ? resolvedThreadId : messageThreadId,
|
||||
isForum,
|
||||
historyKey,
|
||||
historyLimit,
|
||||
|
||||
Loading…
Reference in New Issue
Block a user