Jump to message button in Global search results gives 'Room not found' for thread messages, located not in selected channel

Description:

Jump to message button in Global search results gives 'Room not found' for thread messages, located not in selected channel.
Reproduced not always and sometimes it fixes by itself.

Steps to reproduce:

1. open some channel
2. perform global search for a word, contained in message of the thread which located not in channel from step 1
3. press "Jump to message"

Expected behavior:

Thread opens and the searched message is highlighted.
FYI Thread opens fine if on step 1 you opened channel, in which the thread (from step 2) is located.

Actual behavior:

There are incorrect channels' names shown in global search result. Jumping to message gives "Room not found" error.

Server Setup Information:

Version of Rocket.Chat Server: 4.6.0
Operating System: CentOS Linux release 7.9.2009 (Core)
Deployment Method: yum + src
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: v14.0.0
MongoDB Version: 4.4.13 / wiredTiger (oplog Enabled)
Proxy: nginx/1.20.1
Firewalls involved: iptables, ACCEPT ALL

Client Setup Information

• Desktop App or Browser Version: both
• Operating System: Windows 10

Additional context

Video demo: https://user-images.githubusercontent.com/2260980/162583483-c8e03cd8-c4ad-43c7-8738-1286bf0f8a39.mp4
Our channel and messages in RC are imported from Slack. Maybe this is the cause, but I don't sure.

Relevant logs:

-

Start by reproducing the global-search flow described in the issue: search for a thread message outside the currently open channel and select “Jump to message.” Investigate the channel and thread context used by that navigation; done means the thread opens with the searched message highlighted and no “Room not found” error regardless of the selected channel.