Agents stop seeing queued conversations on manual selection

Description:

Agent cannot see conversations in queue after refreshing the page or changing status to unavailable and back to available

This situation was tested on version 6.0.8 and version 6.1.8, and in both cases the same problem occurred.

I have another environment in version 6.1.8 where this behavior does not occur.

Error video:
https://github.com/RocketChat/Rocket.Chat/assets/11007668/4b2817e6-bc74-4e9b-9d3b-17531552ad3c

Steps to reproduce:

1 - Set up manual selection as the routing method
2 - Start a Livechat conversation with an online agent in the department
3 - Make the agent unavailable
4 - Make the agent available
5 - You will not see the conversation

Expected behavior:

When the agent becomes available, all the conversations in the queue should appear so that he can answer them.

Actual behavior:

The conversations no longer appear in the attendant's queue, and worse, they are lost and can only be retrieved if a manager fetches them from the "current conversations" page.

Server Setup Information:

• Version of Rocket.Chat Server:
• Operating System: RocketChat Cloud
• Deployment Method: RocketChat Cloud
• Number of Running Instances: 1
• DB Replicaset Oplog:
• NodeJS Version: v14.21.2
• MongoDB Version: 4.4.16

Client Setup Information

• Desktop App or Browser Version: Google Chrome 113.0.5672.126
• Operating System: Fedora 38 / Windows 11 / Windows 10

Reproduce the manual-selection Livechat flow described in the issue, including refresh and toggling the agent between unavailable and available. Trace how queued conversations are loaded when the agent becomes available, then verify that the conversations reappear in the queue and remain retrievable without manager intervention.