Away and offline presence information do not update

[Gummikavalier]

Description:

This is a stub issue. I'll update it when I can reproduce it more reliably.

RC web client end stops updating timeout and connection based presence information (away and offline).

Refreshing the web client seems to fix the issue.

Steps to reproduce:

1. Have two users A and B in separate browsers
2. Set user B timeout for away status to minimum (60 seconds) in B's profile
3. Don't focus for user B's browser anymore
4. Follow presence status of user B as user A in the other browser

Expected behavior:

User B's green online presence indicator changes to orange away status after 60 seconds.

Actual behavior:

User B's status remains online forever.

Server Setup Information:

• Version of Rocket.Chat Server: RC 7.11.0
• License Type: Enterprise
• Number of Users: 500+
• Operating System: RHEL8
• Deployment Method: docker
• Number of Running Instances: 4
• DB Replicaset Oplog: Yes
• NodeJS Version: v22.16.0
• MongoDB Version: 7.0.25

Client Setup Information

• Desktop App or Browser Version: Latest Chrome and Firefox

Additional context

Refreshing A's browser window fixes B's false presence status for A.

The issue seems to relate only to automated status updates; If the user B sets the status manually to away, busy, or offline, it updates normally also on A's browser, even when the issue remains active otherwise.

[Aayushdev18]

Hi, I’d like to work on this issue. Could you please assign it to me?

[Gummikavalier]

Have you found out what causes it?

[reetp]

Hi, I’d like to work on this issue. Could you please assign it to me?

In a word, no.

Read all this.

Github & Rocket

Thanks.

[reetp]

User B's status remains online forever.

Think this has been an on/off issue for ages?

When I'm home next week I'll look a bit more.

[Gummikavalier]

I'm also testing with NATS server in our RC deployment. This may or may not have effect on this issue. I'll report back when there is more experience on its effect.

Trigger for this testing was that NATS is recommended by devs for multi-instance setups:
https://forums.rocket.chat/t/troubleshooting-event-propagation-reactivity-issues-in-rocket-chat-7-7-0/22524

[Gummikavalier]

So far no spotted recurrence for this issue with NATS config. For those who run without likely help would be correctly setting TCP_PORT env for internal mesh communication.

[reetp]

TCP_PORT for reference

#36268 (comment)