Rocket.chat: Channels don't always show messages are unread

[jwhiteman36]

Server Setup Information

• Version of Rocket.Chat Server: 3.0.3
• Operating System: CentOS 7
• Deployment Method: tar / extraction
• Number of Running Instances: 11
• DB Replicaset Oplog:
• NodeJS Version: v12.16.1
• MongoDB Version: 3.6.11
• Proxy: Haproxy

We have users reporting that their channels aren't always being highlighted to show that they have unread messages in a channel. It take refreshing the page/application for these channels to become highlighted to show unread messages. I haven't found a way to duplicate the issue yet, it seems to happen randomly for different users.

[Malachiasz]

It sounds like opposite to this bug, where channels sometimes are not being unhighlighted: https://github.com/RocketChat/Rocket.Chat/issues/16920
Maybe it's a general problem with highlighting channels.

[jwhiteman36]

It looks like audio and desktop notifications still work for channels that they are set on even if the channel is never highlighted to indicated unread messages.

[mddvul22]

I think this is a duplicate bug report. See https://github.com/RocketChat/Rocket.Chat/issues/15189

[zdumitru]

See the same thing, even on open.rocket.chat .

[Beeez]

My browser will do this where i will hear the notification sound sometimes but the notification never shows next to the user or group that the message notification was in. Refreshing will show it visually.

[jwhiteman36]

We have found that this is not a problem if we removed readPreference=nearest&w=majority from our configuration. So having all reads go to the primary db resolves the issue, however we recently update to 3.2.1 and started having a lot of performance issues (see #17559 and #17473) so were forced to add the readpreferences back to our configuration causing issues with notifications again.

[BigMayo]

We are having the exact same issue. I will try the work around suggested by @jwhiteman36 and see if that helps, however I fear the performance issues descibed will also be a factor for us.

[BigMayo]

Similar issues: #16920, #15189, #12938
For us, this behavior started happening after a huge forklift upgrade from 1.0.2 to 3.0.12.
I recently upgraded to 3.2.1 to see if this issue would be resolved, but it remains the same.
We are long time Rocket.Chat users and this is causing a serious potential revolt among users. I would hate to have put so much time into this app just to have it replaced with something like google chat. Please help.

[sampaiodiego]

@RocketChat/frontend can you please take a look and also on other similar issues as reported previously? thx

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mddvul22]

Why has this project started threatening to close bugs that have not been addressed?

[tassoevan]

@mddvul22 Because it's fair to assume that an issue report from months ago without many interactions is a regression possibly fixed in the following releases.

[Malachiasz]

Only if the programmers team is rather big in comparison to the project's size. When that's not the case then often very big parts of the codebase are not touched for years.

[mddvul22]

This problem still exists.