Purged threads still show as unread

[sinteur]

Description:

When threads were introduced, we played around with it a bit and disabled it. I had two unread comments in a thread, but after disabling threads the unread counter for the channel was gone. Many releases later, suddenly there was an unread counter for a channel despite the fact that I had read all messages in the channel. Some experimenting later it turned out that when I re-enabled threading, the thread icon had a two unread messages marker. However, since we also have pruning enabled, the old messages were gone, and could not be read, so I am stuck with a "2" badge on the channel that I cannot get rid of.

Steps to reproduce:

1. enable threading
2. have unread messages in a thread
3. disable threading
4. wait until after pruning.

Expected behavior

Unread badges disappear along with pruned messges/threads.

Actual behavior

Unread badges are kept after pruning and cannot be removed as the messages/threads no longer exists.

• Version of Rocket.Chat Server: 3.5.0

• Operating System: linux 3.16.0-10-amd64

• Deployment Method: docker

• Number of Running Instances: 2

• DB Replicaset Oplog: enabled

• NodeJS Version: v12.16.1

• MongoDB Version: 4.0.16

• Desktop App or Browser Version: Any browser. Safari and firefox tested

• Operating System: Mac OS Catalina

[close-issue-app]

This issue was closed because it does not use any of our issue templates. Please make sure to use one of the suggested templates.

[magnetic5355]

Docker 3.5.0

Similar: We have unread thread counts on channels that we cannot clear.

When clicking the channel, selecting threads and filtering for unread, threads appear however opening them does not clear the counter leaving a permanent unread count.

[lyz-code]

We have a similar problem with 3.5.1. Now you are forced to jump into the thread so the notifications are marked as read

[magnetic5355]

Is there a plan to hotfix this? The issue is more noticeable for our user base on 3.6. The rooms with phantom unread counts stay in unread rooms or highlighted on mobile now . Mark as read does nothing creating a lot of confusion on new messages.

[magnetic5355]

Issue still exists - this is the counter after pruning channel to empty. Prior to 3.7 prune did not work on rooms with stuck unread counters - so progress on the issue

[NotACreativeUsername]

Issue is effecting my end users as well. Windows 10 enterprise, Rocket chat version 2.17.11/3.0/3.0.1 and server version Version 3.6.3