Inconsistent User Count in Session After User Reconnection

[anhtv (Van Anh)]

1. Background

We have a RECORDING_BOT user with the following logic:

• It listens to the following events: user-removed, user-added, user-updated, current-audio-change, command-channel-status.
• Upon receiving any of these events, it calls zoomClient.getAllUser() to fetch the current list of users in the session.
• If only RECORDING_BOT is present, it will automatically leave the session.

---

2. Timeline of the Issue

Session ID: xq9W7GA6SnOQpHcj2YglWg==

• The consultant lost network connection.

• After the network was restored, the consultant reconnected.

• Upon reconnection, the consultant’s client called the API: /videosdk/sessions/{session_id}/users. This API call returned 2 users in the session.

• According to the Zoom Dashboard:

  • Consultant left at 06:56:54 JST
  • RECORDING_BOT left at 06:56:54 JST
  • Consultant rejoined at 06:56:54 JST

---

3. Questions

1. When a user (consultant) reconnects, does Zoom actually remove and re-add the user to the session?

   • If yes, could you please provide the exact timestamps (to the millisecond) when:

     • The consultant was removed from the session
     • The consultant was added back

2. At what time did RECORDING_BOT receive the user-removed event for the consultant during this sequence?

   • Additionally, could you confirm the exact timestamp (to the millisecond) when RECORDING_BOT left the session?

3. At 09:56:54.673Z, when the /videosdk/sessions/{session_id}/users API returned 2 users. Did this reflect the actual number of users present in the session at that exact time?

---

We would greatly appreciate your clarification on these points so we can handle session logic accurately in our system.

Thank you very much for your support.

[ticorrian.heard (Ticorrian)]

Hi @anhtv on reconnect, another instance of the same user is created with a unique user id. This is reflected in the dashboard but the API will return the current amount of users in the meeting which in this case was 2 since the meeting bot left (at 06/18/2025 09:56:54:231 according to the server).