Message counter isn't disappearing after reading the message

Description:

I faced a annoying bug. A notification counter appeared when somebody chatted to me. After reading the message, the counter didn't disappear, and even right-clicking and marking as read, the counter still is there.

If that person speaks to me, the counter increases, but when I enter the conversation, the counter sets to "1" again.
If tried to reload server, reload page without cache, and opened desktop and other browsers, that counter is on everywhere.

Steps to reproduce:

There is no way to reproduce it, is just this conversation what remains as unread

Expected behavior:

The counter should disappear, or at least, when I mark the conversation as read, it should force counter to be reset.

Actual behavior:

Counter stays at "1"

Server Setup Information:

• Version of Rocket.Chat Server: 3.11.0
• Operating System: Debian 10
• Deployment Method: source
• Number of Running Instances: 1
• NodeJS Version: 12.18.2
• MongoDB Version: 4.0.19

Client Setup Information

• Desktop App or Browser Version: all versions
• Operating System: all OSes

Relevant logs:

I20210209-14:01:11.896(1) server.js:204 Meteor ➔ method readMessages -> userId: Qjvc83g9tPWkS4fti, arguments: ["NuXEcqxXRkwwwMzxAQjvc83g9tPWkS4fti"] 
I20210209-14:01:14.192(1) server.js:204 Meteor ➔ method readMessages -> userId: Qjvc83g9tPWkS4fti, arguments: ["NuXEcqxXRkwwwMzxAQjvc83g9tPWkS4fti"] 
I20210209-14:01:15.708(1) server.js:204 Meteor ➔ method readMessages -> userId: Qjvc83g9tPWkS4fti, arguments: ["NuXEcqxXRkwwwMzxAQjvc83g9tPWkS4fti"] 

Start with the readMessages method shown in the logs and trace how marking the conversation read updates the notification counter across the server and client. Confirm the behavior with the reported conversation or a comparable unread conversation, then verify that opening or explicitly marking it read removes the counter and that new messages increment it normally.