community icon indicating copy to clipboard operation
community copied to clipboard

Meeting links seem flaky

Open dyladan opened this issue 3 years ago • 18 comments

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?

dyladan avatar Dec 08 '21 18:12 dyladan

@mtwo can you please take a look?

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

SergeyKanzhelev avatar Dec 08 '21 20:12 SergeyKanzhelev

We are facing this right now in the Python SIG. The calendar link zoom page shows this: Screen Shot 2021-12-09 at 12 04 55 PM

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

aabmass avatar Dec 09 '21 17:12 aabmass

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

sanketmehta28 avatar Dec 09 '21 17:12 sanketmehta28

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

dyladan avatar Dec 09 '21 18:12 dyladan

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.

aabmass avatar Dec 09 '21 18:12 aabmass

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.

mtwo avatar Dec 09 '21 18:12 mtwo

🙌 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.

aabmass avatar Dec 09 '21 18:12 aabmass

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.

mtwo avatar Dec 09 '21 18:12 mtwo

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

codeboten avatar Dec 16 '21 17:12 codeboten

Looks like this also occurred for PHP today

mtwo avatar Jan 05 '22 18:01 mtwo

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

bobstrecansky avatar Jan 05 '22 19:01 bobstrecansky

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#!.

mtwo avatar Jan 05 '22 19:01 mtwo

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

cijothomas avatar Jan 11 '22 19:01 cijothomas

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

dyladan avatar Jan 11 '22 19:01 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

dyladan avatar Jan 12 '22 17:01 dyladan

Python today :( Screen Shot 2022-01-13 at 9 02 27 AM

codeboten avatar Jan 13 '22 17:01 codeboten

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.

image

dyladan avatar Jan 27 '22 13:01 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

dyladan avatar Feb 09 '22 17:02 dyladan

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

codeboten avatar Nov 14 '22 20:11 codeboten