Meeting links seem flaky

[dyladan]

At the JS meeting today, nobody was able to get into the meeting. Some people go the error "The meeting is scheduled for Thu Jan 1, 2099" and some people got the error "The host has another meeting in progress." I created a temporary zoom room for us to have the meeting, and about 5-10 minutes after the meeting started the meeting room started working again so we moved over there in order to preserve the recording.

@aabmass mentioned they have had similar issues in the python SIG

Could this be related to some limit on our zoom account?

[SergeyKanzhelev]

@mtwo can you please take a look?

@dyladan were you able to use one of the old meeting rooms?

[aabmass]

We are facing this right now in the Python SIG. The calendar link zoom page shows this:

We are able to use the old link now (https://zoom.us/wc/8287234601).

[sanketmehta28]

the issue seems to be with zoom update. After installing latest update from zoom, the meeting link was working fine.

[dyladan]

In JS we had the same issue and I am on the latest zoom. For some reason, the room just starts working after some (unpredictable) period of time

[aabmass]

I am using the web client fwiw (and my company won't let me install the desktop app). Other folks in the meeting were seeing a different error, something about "1/1/2099". What's weird is today the calendar link didn't start working after 5-10 min so we just used the old room.

[mtwo]

Discussed this over Slack this morning, apologies for not responding earlier! I reproduced this on the Python and Swift SIGs after getting notified by @bryce-b over Slack. I think that the 1/1/2099 error is related to how Zoom handles recurring meetings created from Google Calendar and that the "Meeting owner is in another call" is the true error.

I checked / changed our Zoom settings this morning after the meetings took place and regenerated the links. Summary of what I did:

• I attempted to join the meetings and confirmed that I saw these errors. I saw the 1/1/2099 error in the Zoom app and the "Meeting owner is in another call" error when joining from the web client.
• I confirmed that our meetings are configured to allow people to join without the host. This was already the case.
• I found a setting that controls how early non-owners can join a meeting and set it to 15 minutes. It was previously zero.
• I regenerated the Zoom links and tested that I could join the calls.

I'm hoping that this fixes it, though I'm concerned that it may not have. Worst case we can get more Zoom accounts from the CNCF and go back to our old model. Let's try this for the next few weeks; please ping me on this issue (by re-opening it and @ mentioning me) or on Slack (with an @ mention) ASAP if it reoccurs.

[aabmass]

🙌 thanks @mtwo!

One small question

I found a setting that controls how early non-owners can join a meeting and set it to 15 minutes. It was previously zero.

Who is owner in this case and when do the meetings "start"? We were running into this during the meeting also, not just before.

[mtwo]

Good question, I had the same thoughts, which is why I'm not confident that I understand the root cause of the issue. The owner is a zoom account called cncf-opentelemetry-1, which nobody should be signed in as. Basically, this owner has never joined any meeting, but we only started running into trouble yesterday for some reason.

[codeboten]

Ran into this problem again this morning at the Python SIG meeting :(

[mtwo]

Looks like this also occurred for PHP today

[bobstrecansky]

Yup; @mtwo - thank you for fixing our link in the calendar.

[mtwo]

Unfortunately I'm no closer to understanding why this is happening. The only course of action that is guaranteed to fix this is going back to multiple Zoom accounts and spacing out our meetings. I'll try to debug this further before pursuing that, though it looks like it may be a core Zoom issue: https://community.zoom.com/t5/Marketplace/Google-Calendar-Plug-in-Date-Issues/td-p/2857#!.

[cijothomas]

+1 - We hit this issue in .NET SIG meeting today as well. We used a temporary zoom meeting link from past to workaround temporarily.

[dyladan]

Do we have a contact at zoom that can help us out with troubleshooting? If not, should we try to get one?

[dyladan]

JS meeting had the issue again. This is the issue I see:

The meeting is scheduled for Thu, Jan 1 , 2099.

Start at 3:00 AM This is a calendar meeting

[codeboten]

Python today :(

[dyladan]

JS was not able to have our meeting on the regular zoom call at all yesterday and I had to generate a link on my own. Because of that the call was not recorded.

[dyladan]

Same thing on JS this week. We have not had a successful JS meeting in a month or so now without creating a private zoom on our own

[codeboten]

I've not heard of this happening recently, can the issue be closed?