Read receipts not showing as read even when all present have read

[reetp]

Description:

Read receipts enabled

When all users in a channel have read their messages we still do not get 2 blue ticks on some channels.

I have some channels where we have a few users that have not changed, and that go back several years, and always read receipts go blue when we have all read messages.

However some channels stubbornly refuse to be 'read' even when all the users in the channel are online and have read a message.

I believe this may be due to deactivated users somehow.

Steps to reproduce:

1. Send a message
2. Note it is still a single tick/grey
3. Check who has read it
4. Note that despite being read by all active users in channel it is still not blue ticked

Expected behavior:

If all active users in channel have read a message it should be double blue ticked.

Actual behavior:

Ticks stay grey despite all active users reading the message.

Server Setup Information:

• Version of Rocket.Chat Server: 6.7.2
• License Type: Starter/EE
• Number of Users: various - < 100
• Operating System: Linux
• Deployment Method: docker
• Number of Running Instances: 1
• DB Replicaset Oplog: Yup
• NodeJS Version: As per docker
• MongoDB Version: 7.0.x

Client Setup Information

• Desktop App or Browser Version: Both Firefox/Chromium/App

• Operating System: -Linux

Additional context

I have checked on both an EE and a Starter setup I manage.

Seems to reproduce.

Both servers have a number of deactivated users.

I am wondering if they got messages that went unread after they left the business but before they were removed from the channel?

There seems to be no method to say 'Mark all as read for all' or 'Clear read messages for deactivated users' to reset the counters.

[programmiererei]

I got the same problem with v7.7.0, Starter, Channel with 2 Users; WebClient 4.5.0, IOS Client. Feature stopped working without any reason:

[blazethunderstorm]

@reetp can I try to work solve this issue ?

[reetp]

@reetp can I try to work solve this issue ?

Don't @ people.

I don't work here. I get notified anyway so don't need my phone pinging relentlessly.

You can do what you want but be aware the team is looking into this, it's probably quite major work, and the bar to get a PR accepted will be high.

[salihudickson]

hey, I've taken a look at this issue and, you're right that the issue is caused by the fact that deactivated users cannot read the messages. And I've created a PR to fix that. Although I'm not sure who to @ to get it looked at.

[reetp]

And I've created a PR to fix that.

Ok thanks.

Although I'm not sure who to @ to get it looked at.

You don't need to @ anyone. The relevant people will see it.

I'll raise it with the team but, as per my previous, the bar for accepting this will probably be high.