RocketChat / RocketChat/Rocket.Chat

Away and offline presence information do not update

Open
#37,288 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is identified in the issue. Start by reproducing the two-browser scenario with a 60-second away timeout and compare automated presence updates with manual status changes. Done means the observed user changes from online to away and offline without refreshing the other browser.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.