TL;DR

Adjust the check order in resolveMattermostReplyRootId and resolveMattermostEffectiveReplyToId functions to prioritize threadRootId over kind === "direct".

Guidance

• Review the resolveMattermostReplyRootId and resolveMattermostEffectiveReplyToId functions in auth-profiles-*.js to understand the current logic flow.
• Modify the condition checks to ensure threadRootId is checked before kind === "direct", allowing DM replies to be correctly routed to the main DM channel or the existing thread.
• Verify the fix by testing DM replies in both the main DM channel and within threads, ensuring replies appear in the expected location.
• Consider adding logging or debugging statements to monitor the threadRootId and kind values during the reply process to help identify any further issues.

Example

// Example adjustment in resolveMattermostReplyRootId function
if (threadRootId) {
  // Use threadRootId to determine reply location
} else if (kind === "direct") {
  // Handle direct messages without a threadRootId
}

Notes

This fix assumes that the threadRootId is correctly set for DM thread messages and that the issue is solely due to the check order in the mentioned functions.

Recommendation

Apply the suggested workaround by adjusting the check order in the resolveMattermostReplyRootId and resolveMattermostEffectiveReplyToId functions, as this directly addresses the identified root cause of the issue.