we are monitoring leave_time for participant left and start_time for participant joined. start_time for meeting start and end_time for meeting end. they are delayed by about 30 minutes.
we do not see any service status issues posted at status.zoom.us. Wondering if our webhook notifications may be delayed by some kind of rate limits? Thank you for any information you can provide
So, one month and a half later after this ticket, looks like this webhook delay thing is still around.
We are experiencing the same issue with the “participant/host left meeting” webhook which seems to be triggered in a completely unpredictable way, sometimes almost immediately, sometimes after a few minutes, sometimes a few hours, sometimes … never.
On the other hand, the “Participant/Host joined meeting” webhook is almost always triggered immediately. Which makes things event more weird.
Of course, everything is all green on the status.zoom.us page.
Apparently, there are tickets about this issue all the way down to march… Do we have hope it will be resolved one day ?
We are seeing the same thing. Webhooks are often being delayed. Sometimes they don’t arrive at all.
I can post an example today.
We received meeting.started for meeting uuid PC4NnHyWS+uwZs32v2YHYQ==\ at 2020-07-07 15:03:00 UTC
Few minutes later we receive recording.started for the same meeting. Webhook was received at 2020-07-07 15:08:26 UTC
However recording is set to start automatically with the meeting and in this case we saw the recording indicator on but received the webhook 5 minutes later.
I agree with the post above. We receive webhooks a few hours late sometimes. It’s completely unpredictable and unreliable.
Hey @tommy,
Could you please check a meeting for us “f3oNcM40TvWAKQ+23TISXg==”
We didn’t receive the recording.started webhook again. Can you please check if the meeting actually recorded? Do you see the webhook being sent on your end?
After looking at the logs, the meeting started at 2020-07-08 19:00:25(GMT), and the meeting didn’t ever start recording, so there wasn’t a meeting recoding started event webhook.
Thanks for confirming that. It’s very hard to track these issues. We talked to the client and they claim that recording was on and that recording is configured to start automatically for all their meetings.
From our end we see the recording was never started, so maybe they changed their settings for the meeting. Let us know if you see this issue happen again and we will look into it.
We are also seeing significant delays in our webhooks being fired, specifically for meeting.registration_created, which just took over 7 minutes to fire.