Description
Short description: We have had two users who when trying to start the meeting have received the error “If you are the meeting host, sign in to start the meeting (Meeting ID)” or “You cannot start the meeting (Meeting ID) because it is hosted by another user”.
One user had the “You cannot start the meeting (Meeting ID) because it is hosted by another user” error on the day and time the meeting was due to start, but then a day later when it had finished when i used clicked the url it worked.
We have been using the API for 6 months and haven’t had issues until the last 2-3 days with these users. Nothing in the code for how we handle Zoom has changed. When we create a meeting, the start_url works, after a while it no longer recognises us as the host / logged in at all. But this seems to be random.
Long Description: After receiving these errors we began to look into the issue. Upon researching the situation we have found situations where we would schedule a class and the provided start url would work. Then we would wait a bit and it wouldnt work. Then we would come back and it would work, and then suddenly not work again. So the crux of the matter, without any reason at all Zoom does not recognise us as the host of the meeting sometimes and makes us sign in. Even for the same link this happens seemingly randomly.
Stuff we have confirmed:
- custCreate: All of our users, including the ones we used when testing are custCreate users so the start url should last for 90 days. We do not think it is an expiry issue.
- API: Running the get meeting
API which returns a new start_url allows us to start the class. But the start url returned by the create_meeting
API does not.
- Browser cache: Can confirm not cache related. Happens in all browsers and in incognito mode.
- Timezones: timezones are set correctly and confirmed not to be an issue (such as meetings scheduled for a different time and people technically joining the class late)
- Start time: Happens to meetings in the future, meetings in the past. Randomly. MOST of our meetings in the past are fine and work. MOST of our meetings in the future are fine and work too. There does not seem to be a connection as to why this is happening.
- End time: Some meetings randomly have an end_time or dont have an end_time. Even if they have already finished. This does not seem to relate to the issue we are having though as it occurs on meetings with and without end_time in the payload.
We can find no logical consistency for what is causing the start_urls to work or not work through our testing. It seems to be random.
Here is a payload we tested:
`{'id': '95617216864',
'type': 2,
'uuid': 'yA0ktza4T/uJy43+XueldA==',
'topic': 'Krasi testing stream',
'status': 'waiting',
'host_id': 'f5o-pA9zTPWz0EqA1Tf17g',
'duration': 60,
'join_url': 'https://zoom.us/j/95617216864?pwd=SGNtUHBGWXBtWXdmSEJJU3l2cHpzZz09',
'password': 'F3ssoRiP8l',
'settings': {'audio': 'voip',
'use_pmi': False,
'watermark': False,
'cn_meeting': False,
'host_video': True,
'in_meeting': False,
'contact_name': 'contact name here',
'waiting_room': False,
'approval_type': 2,
'contact_email': 'email address here',
'enforce_login': False,
'auto_recording': 'none',
'encryption_type': 'enhanced_encryption',
'mute_upon_entry': True,
'join_before_host': True,
'alternative_hosts': '',
'participant_video': False,
'show_share_button': True,
'close_registration': False,
'enforce_login_domains': '',
'allow_multiple_devices': True,
'meeting_authentication': False,
'registrants_confirmation_email': True,
'registrants_email_notification': False,
'request_permission_to_unmute_participants': False},
'timezone': 'Europe/Sofia',
'start_url': 'https://zoom.us/s/95617216864?zak=eyJ6bV9za20iOiJ6bV9vMm0iLCJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJjbGllbnQiLCJ1aWQiOiJmNW8tcEE5elRQV3owRXFBMVRmMTdnIiwiaXNzIjoid2ViIiwic3R5IjoxLCJ3Y2QiOiJhdzEiLCJjbHQiOjAsInN0ayI6IjA2WHVwT0NfM0hUZkhSdjNwdWpsM1Q1LTl6UXoxQzBBQWMxWG1RRV9LQjguQUcuMGxXYkx6cWxWS2dsaXpheF9jYUtEbzkybHNvUHUzVm01OUt2a2IzMG1FUk5YNm9yNlBMYTcxSzM3TEhqbnhPU3IxMlREeW42NkQtbFIyTS5KMkFkak12T3liYjZVMGxRT3pPeFdBLklQVmhfQU5WVUx0NlFVTDUiLCJleHAiOjE2MDQ2NTkzMTMsImlhdCI6MTYwNDY1MjExMywiYWlkIjoiN19NeGhBUHdRZGFUV3BpOVJPTzR4USIsImNpZCI6IiJ9.84ha0m-m--SfQrE_CB99yGz8RGi75IBs0qfx1EgKUIw',
'created_at': '2020-11-06T08:41:53Z',
'host_email': 'email address here',
'start_time': '2020-11-06T13:00:00Z',
'h323_password': '8281103215',
'pstn_password': '8281103215',
'encrypted_password': 'SGNtUHBGWXBtWXdmSEJJU3l2cHpzZz09'}`
Error
“If you are the meeting host, sign in to start the meeting (Meeting ID)” or “You cannot start the meeting (Meeting ID) because it is hosted by another user”.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT App
Which Endpoint/s?
Using https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate and https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meeting
How To Reproduce (If applicable)
Steps to reproduce the behavior:
Not able to see a logical way to reproduce this. But it only took an hour or two of investigating to have the error happen to us. But there is no logical reason to it.