# On connection change fail repeated for just one user

**URL:** <https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215>\
**Category:** Video SDK\
**Created:** [June 19, 2025, 11:16pm UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215 "2025-06-19T23:16:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![David30](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david30/32/54536_2.png) [@David30](https://devforum.zoom.us/u/David30)\
**Post date:** [June 19, 2025, 11:16pm UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/1 "2025-06-19T23:16:35Z")

</div>

Video SDK web v2.2.0

One of our users has been getting kicked out of their sessions. We see that the on connection change event is firing twice: once with reconnecting failover and then with connection state fail. I have read the forum post “Clarification on connection-change behavior with fail state and failover reason” (won’t let me link) and initially thought it might be the a connection issue with the user. However, this pattern happens every time the user enters a session.

For additional context, they are using a Samsung Galaxy phone and cellular data. I would appreciate it if you could take a look at what might be causing this issue. Also, this does not happen to any other user.

Thanks

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [June 20, 2025, 1:24am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/2 "2025-06-20T01:24:12Z")

</div>

Hey @David30

Thanks for your feedback.

Could you share some problematic session IDs with us for troubleshooting purposes?

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![David30](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david30/32/54536_2.png) [@David30](https://devforum.zoom.us/u/David30)\
**Post date:** [June 20, 2025, 2:15am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/3 "2025-06-20T02:15:38Z")

</div>

Yes, two session ids are  
b18881cc-55bc-4528-8deb-3ba380910718  
andbe65f5eb-432a-45c4-a71b-f22791dffb12.

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [June 20, 2025, 3:33am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/4 "2025-06-20T03:33:26Z")

</div>

Hi @David30

> b18881cc-55bc-4528-8deb-3ba380910718  
> andbe65f5eb-432a-45c4-a71b-f22791dffb12.

It seems these are not valid session IDs. You can retrieve the correct session ID from the web portal under **Dashboard** , or if you’re currently in a session, you can get it programmatically by calling `client.getSessionInfo().sessionId`.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![David30](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david30/32/54536_2.png) [@David30](https://devforum.zoom.us/u/David30)\
**Post date:** [June 20, 2025, 5:57am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/5 "2025-06-20T05:57:57Z")

</div>

Sorry I was looking at the wrong id. Let me know if this works:  
4Wf96Ma0Sp6vNtkBYMqEpg==  
cwSIOzT+TduQqP2c+RDhfA==

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [June 23, 2025, 3:10am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/6 "2025-06-23T03:10:50Z")

</div>

Hi @David30

> 4Wf96Ma0Sp6vNtkBYMqEpg==

After analyzing the logs, we didn’t observe repeated reconnection attempts in this session. We only saw that one user left the session shortly after joining, which might have been due to closing the browser.

> cwSIOzT+TduQqP2c+RDhfA==

This session occurred over a month ago, and we’re unable to retrieve its detailed logs because detailed logs are only retained for one month.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![David30](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david30/32/54536_2.png) [@David30](https://devforum.zoom.us/u/David30)\
**Post date:** [June 27, 2025, 3:30pm UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/7 "2025-06-27T15:30:11Z")

</div>

Hi @vic.yang

That is strange as it doesn’t match the reported flag and the events we got from the connection change event. Would you be able to look at this session: T9snPBaiT0G1l6LckzQuRA==

Seems like similar problems happened to one user in that session. Thanks again!

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [June 30, 2025, 1:17am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/8 "2025-06-30T01:17:51Z")

</div>

Hi @David30

> T9snPBaiT0G1l6LckzQuRA==

After analyzing the logs, we found that userID 16791552 (on Windows Edge) experienced a network-induced reconnection approximately 6 minutes after joining the session. However, the reconnection failed because the JWT token had expired.

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 1, 2025, 2:18am UTC](https://devforum.zoom.us/t/on-connection-change-fail-repeated-for-just-one-user/134215/9 "2025-07-01T02:18:24Z")

</div>

Closed on July 1, 2025, 2:18am UTC

This topic was automatically closed 25 hours after the last reply. New replies are no longer allowed.
