# Join meeting error after host ends the session (Continued) **URL:** \ **Category:** Web\ **Created:** [May 8, 2025, 9:57am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504 "2025-05-08T09:57:59Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![lmtruong1512](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lmtruong1512/32/59233_2.png) [@lmtruong1512](https://devforum.zoom.us/u/lmtruong1512)\ **Post date:** [May 8, 2025, 9:58am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/1 "2025-05-08T09:58:00Z")
**Description** Following up on this thread: [Join meeting error after host ends the session](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session/122226) We’re still encountering an issue in version 2.1.0 where, if the host ends the meeting (`client.leave(true)`) and a guest attempts to join at the same time, the guest receives the following error: ```auto {“type”: “JOIN_MEETING_FAILED”, “reason”: “meeting ended”, “errorCode”: 4004}` ``` Is there a plan to address this behavior in a future release? Additionally, could you please check whether the same issue is affecting the following session IDs where users experienced join errors? These session IDs may have encountered errors: ```auto 1326794411_1744875132711 E2l6GHhYShKo8IIbLHPFqw== 21Hy3rwQRhSNcNICWF4C1A== 5439510715_1745367543958 +I8kR0v0RIyiPV5/K77WTQ== LIcutEfaRuqoglTkzUshjw== 4614461147_1743645461473 I/XPZsGCQtGAG/HPWqzvcw== 41pztyPMTIyQXHXPV9KZcA== 0751860355_1743567075190 zRzujM+zSiqjcOeKO99lNA== epiatw9ySfuI4/mIjbKbGw== bP6Ka2jHTl68z9/sEo1kJQ== csehIZ4HTFCy87/R58qyaA== 9866513403_1746686986656 w6Pr3XQETFOnwwTqqo2Scw== dJ53Dy38RDG4+e6OOAUmiQ== 7GyACuT7SDCMxwP29jUErg== 73/MCg0USE2ZrXd/VKWfgA== ``` Thank you! **Which Web Video SDK version?** 2.1.0 **Device** - OS: Ubuntu - Browser: Chrome - Version: 134 ---
**Author:** ![lmtruong1512](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lmtruong1512/32/59233_2.png) [@lmtruong1512](https://devforum.zoom.us/u/lmtruong1512)\ **Post date:** [May 8, 2025, 11:23am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/2 "2025-05-08T11:23:02Z")
@vic.yang We’ve encountered the “join meeting” error multiple times in similar scenarios. Would adding a short delay before retrying the `client.join(...)` call be a reasonable workaround while waiting for an official fix? Are there any potential issues or side effects we should be aware of with this approach? ---
**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:** [May 9, 2025, 2:02am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/3 "2025-05-09T02:02:10Z")
Hey @lmtruong1512 > Would adding a short delay before retrying the `client.join(...)` call be a reasonable workaround while waiting for an official fix? For the Video SDK, there is likely no better solution. As mentioned in previous [threads](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session/122226/2), this is a timing issue. Adding a delay for non-host users may not resolve the issue, as users don’t know exactly when the host ends the session — introducing a delay could actually increase the time it takes to join the session. Curious to know — are you always reusing the same topic to join sessions? It might be helpful to use different topics for different sessions, as this could reduce the frequency of this issue occurring. Thanks Vic ---
**Author:** ![lmtruong1512](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lmtruong1512/32/59233_2.png) [@lmtruong1512](https://devforum.zoom.us/u/lmtruong1512)\ **Post date:** [May 9, 2025, 3:13am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/4 "2025-05-09T03:13:47Z")
@vic.yang Thank you for your response, > Adding a delay for non-host users may not resolve the issue, as users don’t know exactly when the host ends the session — introducing a delay could actually increase the time it takes to join the session. I meant is: if we call `client.join(...)` and it throws an error like this: `{ "type": "JOIN_MEETING_FAILED", "reason": "meeting ended", "errorCode": 4004 }` — then we would retry the join after a short delay. This would simulate the case where users join at slightly different times after the meeting has ended. Would this approach work in practice? > Curious to know — are you always reusing the same topic to join sessions? It might be helpful to use different topics for different sessions, as this could reduce the frequency of this issue occurring. Yes, we reuse the same topic to join sessions. But in this case, the host ends the meeting _just as_ a guest tries to join, so we can’t distinguish between sessions — and that makes it difficult to resolve the issue using just the topic. ---
**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:** [May 9, 2025, 5:08am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/5 "2025-05-09T05:08:58Z")
Hi @lmtruong1512 It would be fine if you add a short delay before rejoining. Thanks Vic ---
**Author:** ![lmtruong1512](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lmtruong1512/32/59233_2.png) [@lmtruong1512](https://devforum.zoom.us/u/lmtruong1512)\ **Post date:** [May 9, 2025, 6:50am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/6 "2025-05-09T06:50:41Z")
@vic.yang Thank you for your response, Could you please verify whether the following session IDs encountered the same join errors `{“type”: “JOIN_MEETING_FAILED”, “reason”: “meeting ended”, “errorCode”: 4004}`? Session IDs: ```auto 1326794411_1744875132711 E2l6GHhYShKo8IIbLHPFqw== 21Hy3rwQRhSNcNICWF4C1A== 5439510715_1745367543958 +I8kR0v0RIyiPV5/K77WTQ== LIcutEfaRuqoglTkzUshjw== 4614461147_1743645461473 I/XPZsGCQtGAG/HPWqzvcw== 41pztyPMTIyQXHXPV9KZcA== 0751860355_1743567075190 zRzujM+zSiqjcOeKO99lNA== epiatw9ySfuI4/mIjbKbGw== bP6Ka2jHTl68z9/sEo1kJQ== csehIZ4HTFCy87/R58qyaA== 9866513403_1746686986656 w6Pr3XQETFOnwwTqqo2Scw== dJ53Dy38RDG4+e6OOAUmiQ== 7GyACuT7SDCMxwP29jUErg== 73/MCg0USE2ZrXd/VKWfgA== ``` Thank you for your patience. ---
**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:** [May 9, 2025, 7:22am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/7 "2025-05-09T07:22:48Z")
Hi @lmtruong1512 > E2l6GHhYShKo8IIbLHPFqw== > LIcutEfaRuqoglTkzUshjw== These two sessions had the join error issue. > I/XPZsGCQtGAG/HPWqzvcw== > 41pztyPMTIyQXHXPV9KZcA== > zRzujM+zSiqjcOeKO99lNA== > epiatw9ySfuI4/mIjbKbGw== > bP6Ka2jHTl68z9/sEo1kJQ== > csehIZ4HTFCy87/R58qyaA== These sessions are from over a month ago, and since our logs are only retained for one month, we’re currently unable to retrieve their logs. Thanks Vic ---
**Author:** ![lmtruong1512](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lmtruong1512/32/59233_2.png) [@lmtruong1512](https://devforum.zoom.us/u/lmtruong1512)\ **Post date:** [May 13, 2025, 11:11am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/8 "2025-05-13T11:11:35Z")
@vic.yang We got it, thanks for your support—much appreciated! ---
**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:** [May 13, 2026, 11:12am UTC](https://devforum.zoom.us/t/join-meeting-error-after-host-ends-the-session-continued/132504/9 "2026-05-13T11:12:19Z")
Closed on May 13, 2026, 11:12am UTC This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.