Scheduled meeting disappears from all accounts but stays live on Zoom's servers ("Waiting for host") | Community
Skip to main content
New Member
August 11, 2026
Question

Scheduled meeting disappears from all accounts but stays live on Zoom's servers ("Waiting for host")

  • August 11, 2026
  • 2 replies
  • 54 views

We've had this happen twice now, on separate occasions, with different hosts on our organization's Zoom account:

1. A meeting is scheduled normally (directly via the Zoom web portal, no third-party calendar add-ons involved).
2. It appears correctly in the scheduling account's Upcoming Meetings list at first, and calendar invites go out and work fine.
3. On the day of the meeting, it's gone — not in Upcoming Meetings, not under any other user on the account, and not in Recently Deleted.
4. The original meeting link still works and opens a live session showing "Waiting for host" — so the meeting still exists on Zoom's servers — but no one can log in as host to start it, because it's not attached to any licensed user anymore.

A Zoom Support agent confirmed our scheduling workflow was standard and checked every PMI and scheduled meeting across all our accounts, but couldn't explain why the Meeting ID stays active without being attached to any account.

Has anyone else run into this? Specifically curious whether this can happen due to license reassignment, user deactivation/reactivation, or a user being moved between sub-accounts after a meeting is already scheduled — and if so, whether there's a way to prevent it.

2 replies

jdott16
Community Champion | Employee
Community Champion | Employee
August 12, 2026

Hello ​@Danial Masruroini 

I believe two articles could assist with this issue. 

  1. https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061476 > Waiting for the host to start meeting/webinar
  2. https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0065196 > Frequently asked questions about meeting and webinar IDs

It is possible the meetings are scheduled, and they are not run within the 30 day expiration deadline which could be a cause of this issue.

If ‘Join Before Host’ is not enabled, which it appears is the case for these meetings due to the message being received, then the host would have to be available to start the meeting otherwise the message will continue to appear. 

This issue can also happen if you have license reassignment, user deactivation, as well as users being moved between sub-accounts if the processes used in these cases is not properly followed. You can find out more about account consolidation and moving users from one account to another with the following articles: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0068212 and https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0082467

The best way to get to the bottom of this would be to reach out to support with meeting ID’s that this has occurred with so that Zoom support can run an audit to see who created the meeting, when it was scheduled for, and if there are any issues with that meeting host that could be causing this issue. I understand Zoom Support already looked into this, but there should be more of a concrete explanation and resolution here other than confirming the workflow is correct. They should be able to specifically pinpoint where the issue lies if it persists for users on your account.

I hope this helps and if this answers your question please make sure to mark this as a solution.

 

Thank you,

Jake

New Member
August 13, 2026

Hi Jake,

Thank you so much for the detailed reply — this confirms exactly the direction we suspected. Really appreciate you pointing to license reassignment, user deactivation, and sub-account moves as known causes; that lines up perfectly with our organization's setup (multiple sub-accounts under one shared domain).

I'll follow your recommendation and go back to Zoom Support with the specific Meeting ID(s) so they can run a proper audit on the host account and pinpoint exactly what happened. Marking this as the solution.

Thanks again for the help!

Danial