Loss of authorization (Invalid user)

Description: Periodically, users are kicked out of the desktop application, with an error in the logs. After that, you need to log in again. Authorization expiration in days is set to 0.

Steps to reproduce: The user launches an application or reconnects to the server after the PC wakes up.
Expected behavior: The user continues in the chat application.
Actual behavior: User loses authorization.
Server Setup Information:
Version of Rocket.Chat Server: 5.2.0

• Operating System: Synology

• Deployment Method: docker

• Number of Running Instances: 1

• DB Replicaset Oplog: yes

• NodeJS Version: 14.19.3

• MongoDB Version: 4.4.0
  Client Setup Information

• Desktop App: 3.8.14

• Operating System: Win 7/10/11
  Relevant logs:
  {"level":50,"time":"2022-12-06T02:02:13.394Z","pid":1,"hostname":"rocket.chat","name":"System","msg ":"Exception while invoking method getRoomByTypeAndName 'Invalid user [error-invalid-user]'"}
  {"level":50,"time":"2022-12-06T02:02:14.030Z","pid":1,"hostname":"rocket.chat","name":"System","msg ":"Exception while invoking method createDirectMessage 'Match error: Expected string, got undefined'"}

Start by reproducing the logout when the desktop application launches or reconnects after the PC wakes, then trace the logged getRoomByTypeAndName and createDirectMessage errors through the authorization flow. No source file or test is named; done means users remain authorized and can continue chatting under the reported configuration.