# Bugfix requested in (1308) does not extend to Zoom Rooms

**URL:** <https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335>\
**Category:** Meetings\
**Created:** [January 5, 2026, 7:35pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335 "2026-01-05T19:35:40Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [January 5, 2026, 7:35pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/1 "2026-01-05T19:35:40Z")

</div>

Similar to the issue reported in (1308), using the **PUT: endpoint meetings/:{meetingId}/status** call to end a meeting provides a misleading message to Zoom Rooms (formerly connected, now disconnected) when the meeting ends.

This message reads: “This meeting has ended as someone has started a new meeting with this account”

As our users take any onscreen message seriously, we’d prefer for the messages to be accurate. Can this please be addressed?

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [January 5, 2026, 7:36pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/2 "2026-01-05T19:36:24Z")

</div>

Two threads that reference the behavior:

> [@update meeting status (end) Someone has started a new meeting with this account](https://devforum.zoom.us/t/update-meeting-status-end-someone-has-started-a-new-meeting-with-this-account/1308):
>
> When I use the PUT:&nbsp; endpoint meetings/:{meetingId}/status (replacing meeting Id), to end a meeting, the user gets a weird error on their call as you can see on the image, this shouldn’t be, as it was ended with the API endpoint, not someone starting another meeting with the same account

> [@This meeting has ended as someone has started a new meeting with this account](https://devforum.zoom.us/t/this-meeting-has-ended-as-someone-has-started-a-new-meeting-with-this-account/18094):
>
> Description When a meeting is ended from an API call user can see misleading message on screen by zoom client. Error This meeting has ended as someone has started a new meeting with this account Which App Type (OAuth / Chatbot / JWT / Webhook)? OAuth Which Endpoint/s? [https://api.zoom.us/v2/meetings/{meetingId}/status](https://api.zoom.us/v2/meetings/%7bmeetingId%7d/status) How To Reproduce (If applicable) Steps to reproduce the behavior: Create a zoom meeting try to end the meeting by invoking the API [https://api.zoom.us/v2/meetings/{meeti…](https://api.zoom.us/v2/meetings/%7BmeetingId%7D/status)

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 21, 2026, 7:51pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/3 "2026-01-21T19:51:28Z")

</div>

Hey @bstrelko  
Sorry for the late reply here, would you be able to share with me a tracking ID of a request you made to end a meeting where you got the message:  
“This meeting has ended as someone has started a new meeting with this account”

I tracked some of the previously reported issues and they are closed and reported as fixed. So I would love to escalaate this to the right team.

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [January 22, 2026, 3:27am UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/4 "2026-01-22T03:27:45Z")

</div>

Hey, @elisa.zoom - will look to get this to you shortly. I believe the reported remediation (like many) was focused on the core desktop client - not Zoom Rooms, everyone’s favorite Zoom product to ignore - which is why the issue was never addressed.  
The issue I’m reporting has specifically been observed on Zoom Rooms hardware.

I’ll aim to repro in the next few days and get you that tracking ID immediately afterward. Thanks for looking into this!!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 22, 2026, 3:03pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/5 "2026-01-22T15:03:54Z")

</div>

@bstrelko thanks a lot! I will make sure to escalate this as soon as I get that data from you and will make sure to prioritize this!  
Thanks for your help

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [January 22, 2026, 5:17pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/6 "2026-01-22T17:17:49Z")

</div>

```auto
"v=2.0;clid=aw1;rid=WEB_af744cb8067c0f9e56690c69a354f915"

```

@elisa.zoom - just performed this call and validated behavior.  
To be clear - the message is shown on the Zoom Room’s primary display, not returned via API. Thanks!

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 23, 2026, 2:19pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/7 "2026-01-23T14:19:03Z")

</div>

> [@bstrelko](#):
>
> `"v=2.0;clid=aw1;rid=WEB_af744cb8067c0f9e56690c69a354f915"`

Thanks a lot for sharing that with me.  
I created an internal ticket with our Engineering team (ZSEE-192514 internal ticket number for your reference)  
I will update you as soon as I hear back from them

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 27, 2026, 6:43pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/8 "2026-01-27T18:43:28Z")

</div>

Hi @bstrelko

Thanks for your patience here, I’ve received feedback from our Engineering team

The message you’re seeing can occur for several reasons and is not specific to Zoom Rooms . One common cause is insufficient licenses on the account. Since a single user can only host or join one meeting at a time, issues may arise if a user attempts to host multiple meetings simultaneously or if the number of hosted meetings exceeds the available licenses.

In such cases, this alert may appear not only for ZR but for other participants as well.

Please let me know if you have any questions or need further clarification.

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [January 27, 2026, 8:03pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/9 "2026-01-27T20:03:51Z")

</div>

Thanks, @elisa.zoom - I can confidently say that the described cause is not at play in my environment and specific use-case.

- Insufficient licenses - FALSE, more than 50 available
- User attempting to join multiple meetings - FALSE, issue arises when a meeting’s status is changed to ‘end’, no attempt is made to join multiple meetings
- Number of hosted meetings exceeds available licenses - FALSE

You mentioned that the eng team said we can see this message for ‘several reasons’ - what are the other ones?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 27, 2026, 8:36pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/10 "2026-01-27T20:36:39Z")

</div>

> [@elisa.zoom](#):
>
> ZSEE-192514

Thanks for sharing this, I will update our Engineering team

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 28, 2026, 1:41pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/11 "2026-01-28T13:41:28Z")

</div>

Hi @bstrelko  
Would you be able to share the following:

- Meetings details and ZR logs with Error Screenshot/recording and what operation you do in detail(steps to reproduce) to confirm.

We can try to reproduce for this case and check logs for more details. Also customer need to share Body of API and endpoint being called. With just Error message its hard to find root cause.

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [January 28, 2026, 3:17pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/12 "2026-01-28T15:17:55Z")

</div>

Happy to send a video walking through the issue and demonstrating onscreen. Can you please move this conversation to a DM, @elisa.zoom ?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [January 28, 2026, 3:30pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/13 "2026-01-28T15:30:18Z")

</div>

Absolutely, let me send you a DM

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 26, 2026, 1:23pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/14 "2026-03-26T13:23:34Z")

</div>

Hi @bstrelko  
Thanks for your patience here!  
I just wanted to update you about the ticket ZSEE-192514 where I reported the issue you shared with us.  
It seems like this was fixed over the weekend. Could you please try and replicate the behavior you were seeing to confirm if this was resolved?

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [April 6, 2026, 2:40am UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/15 "2026-04-06T02:40:21Z")

</div>

Apologies for the delay, Elisa - will look to validate this fix in the next few days!

Thanks again,  
-Brian

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [April 6, 2026, 10:06pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/16 "2026-04-06T22:06:54Z")

</div>

Confirming that the message now reads “This meeting has been ended by host.” in Zoom Rooms 7.0.1 (9561). Technically this isn’t accurate either, as the host did not end this meeting, but it’s a step in the right direction. @elisa.zoom , are you able to relay our feedback to the team?

We would prefer either of the following:  
“This meeting has been ended via API.” - most accurate  
“This meeting has been ended.” - still accurate, can be used for all instances where the meeting has been ended, not just API-initiated status changes.

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [April 7, 2026, 5:29pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/17 "2026-04-07T17:29:07Z")

</div>

Also worth noting what’s shown on the dashboard when this API call ends a meeting:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/c/8/c83fb0bcc38856040e3bee49cc1e4b6b5870f945.png)

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [November 16, 2026, 7:38pm UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/18 "2026-11-16T19:38:41Z")

</div>

Hi @bstrelko  
I was out on leave and just resuming work.  
Happy to reconnect if there are any open issues we need to look into

---

<div class="post-metadata">

**Author:** ![bstrelko](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bstrelko/32/43750_2.png) [@bstrelko](https://devforum.zoom.us/u/bstrelko)\
**Post date:** [November 17, 2026, 1:37am UTC](https://devforum.zoom.us/t/bugfix-requested-in-1308-does-not-extend-to-zoom-rooms/140335/19 "2026-11-17T01:37:54Z")

</div>

Thanks for following up, @elisa.zoom - no changes since my comments on April 6 and April 7. Better than we were at the start of the ticket, but still inaccurate informational messaging.
