Workspace Panel Does Not Reflect Active Users Connected via API

Workspace Panel Not Reflecting API-Connected Active Users (Potentially Related to Issue #20060)

Description:

Workspace panel does not reflect the correct number of active users when users are connected via the API. Despite having users set as active, the Workspace panel displays zero users online, busy, or away. However, the Users panel correctly lists these users as active or pending.

Steps to reproduce:

1. Connect multiple users via the API and set their status to active using login_rocket_api.
2. Connect additional users via the browser interface.
3. Check the Workspace panel for user activity.
4. Verify user activity in the Users panel.

Expected behavior:

The Workspace panel should accurately reflect the number of users online, busy, or away, including users connected via the API.

Actual behavior:

The Workspace panel displays zero users online, busy, or away, while the Users panel shows multiple users connected (e.g., 2 users via the browser and 15 users via the API). This inconsistency persists despite users being set as active.

Screenshot of Workspace Panel:

Screenshot of Users Panel:

Server Setup Information:

• Version of Rocket.Chat Server: 7.2.0-develop
• License Type: Starter
• Number of Users: 30+
• Operating System: Linux
• Number of Running Instances: 2
• DB Replicaset Oplog: Enabled
• NodeJS Version: v20.18.0
• MongoDB Version: 7.0.5 / wiredTiger

Client Setup Information:

• Desktop App or Browser Version: Multiple browsers
• Operating System: Windows/WSL

Additional context:

The issue creates a discrepancy between user activity as displayed in the Workspace panel and actual user connections managed via the API and browser. This makes it challenging to monitor real-time user activity effectively.

Relevant logs:

No error logs were identified during the testing. However, the following information is present in the Workspace panel:

• Online users: 0
• Busy users: 0
• Away users: 0
• Offline users: 0

Please let me know if additional logs or context are needed to investigate further.

Start by reproducing the discrepancy with users connected through login_rocket_api, then compare the activity data shown in the Workspace panel with the Users panel. Trace how API-connected users and their online, busy, and away statuses are counted; the work is done when the Workspace panel reflects those users consistently.