Channels don't always get marked as read when entered

[Gummikavalier]

Description:

Since Rocket.Chat version 2.0.0 we're experiencing issues where the channels having only few new messages in them don't get marked as read automatically, leaving the channel name as bolded in the channel list pane.

Steps to reproduce:

1. There is a new message on the channel. The channel name has turned into bold to indicate this.
2. The user clicks on the channel and sees the new message on the message pane.

Expected behavior:

The channel should get marked as read and its name in the channel list pane should turn to normal (not in bold).

Actual behavior:

The channel name stays as unread and as bold in the channel list pane.

User can clear this unread status by pressing 'ESC' key to mark the channel as read immediately. Sometimes the this happens automatically when the user waits for a prolonged time (20 seconds), but not always.

In addition to pressing ESC key, also switching tabs in the browser immediately marks the currently open channel as read.

Server Setup Information:

• Version of Rocket.Chat Server: 2.1.0
• Operating System: CentOS7
• Deployment Method: tar
• Number of Running Instances: 20
• DB Replicaset Oplog: Enabled
• NodeJS Version: v8.15.1
• MongoDB Version: 3.6

Additional context

The issue seems to triggers easier on channels that have threads on them.
The issue has been noted on both Chrome and Firefox browsers.
The user amount, server load, disk latency or the amount of memory or cores does not seem to affect the probability of the issue happening.

[stoficek]

I can confirm that since upgrading to 2.0.0 and mongoDB to 4.0.12 messages are not always marked as read.
With upgrading I also migrated rocketchat from Vmware to Proxmox but I dont know if this has something to do with this issue.

[jerbra]

My organization just upgraded this Monday to the latest version deployed via docker-compose and are experiencing the same behavior reported here since the upgrade.

[xbiafra]

Same issue here with 2.1.1 version.

[marcinkorzycki]

+1 on 2.1.1

[waiting-for-rocketchat-fixes]

Same here at my instance ;( 2.1.1

[rjozwiak]

+1 on that

[usmanpm]

+1. I have to click the options button next to the person/channel name and click 'Mark Read' to make the notification go away. Very annoying.

[lehrhardt]

Updated to 2.1.x this week and seeing this with our user base as well. There is not a really clear pattern when this happens. Our user notice this problem with browser and client on different os.

Pressing "ESC" in the rooms, fixes the problem here too.

[Gummikavalier]

I think that when somebody starts writing on the currently open channel ('xxxxx is typing...' when it wasn't there already at which point that may get stuck too I think), or when some other channel gets a new message, and its position or message amount is changed on the left pane, both of these seem to clear up the unread status of the channel as well. The other two being clicking any other tab or bringing the browser window back to focus.

So the more you have active channels in rocket.chat, and more you switch between different windows on your desktop, the higher is the likelihood of something else refreshing the unread status instead of (assumed) actual timer method purposed for it. This makes this issue seem much less common than what it really is.

[krf]

Still a problem in 2.2.0. No clear pattern when it happens, to be honest.

[rsimai]

I can confirm this for 2.2.0. We see this massively after an update from 1.3.2 where it didn't happen. No clear pattern.