Meeting event meeting.participant_left not triggered

[vijayk.kannan (Vijay)]

Description
When participant left the zoom meeting we are not getting webhook event “meeting.participant_left” , we used to get that earlier recent changes break this ?

Error
The full error message or issue you are running into.

Which App Type (OAuth / Chatbot / JWT / Webhook)?
webhook

Which Endpoint/s?
https://provider.ortholive.com/zoomEvents

How To Reproduce (If applicable)
Steps to reproduce the behavior:

1. Request URL / Headers (without credentials) / Body
2. See error

Screenshots (If applicable)
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[tommy (Tommy Gaessler)]

Hey @vijayk.kannan ,

Can you please provide your app ID? (The ID in the url when viewing your app on the marketplace)

We will look into this as one other person reported the same issue today:

Two WebHook features

Description I have created an app that now has two event webhooks. I am doing this so I get my app ready for publication outside of running it in our production site. Error It seems that I do not get all webhooks. I seem to get getting the start and end meeting event ok. But I don’t get the all the user join/leave events. I am wondering if all webhooks will be called regardless of how many others are created. Like if a 200 is returned from the first webhook will it still call the second webho…

(ZOOM-130438)

Thanks,
Tommy

[saro]

I can also chime in and confirm that this is indeed occurring (tested using webhook.site, locally, and with production on Zapier to make sure, and we’ve had our app case working fine for many months). The meeting.participant_left endpoint that fires via. webhook has mysteriously stopped firing in the last ~1-2 days or so.

All the other events are fine (such as meeting.ended and meeting.participant_joined works fine – i.e. the join event fires successfully) – but not having the leave event breaks our app case (where one can see if a user in our org joins/leaves the room after we serialize the data).

Here’s an example of how the serialized event looks to the end-user (join event, of course, the leave event isn’t working right now):

@tommy: Because of this not working, we only see join events which is rather annoying to the end-user. I saw you asked the original poster for his app ID’s. Our app case is private, but the ID’s are: 6RAlVUrUTOiUB1aj-ajghg for our Dev (unserialized) and YasIjPmBQei0JT9JGl3zoA for our serialized webhook (one subscribes to more events).

Thanks, Tommy. Will really be on the look for an update (…or it’ll just start working again, hah). Cheers

[tommy (Tommy Gaessler)]

Hey @saro, thanks for the detailed post!

I’ve sent this info to our engineers and we are working on a fix.

Stay tuned!

Apologies for the inconvenience,
Tommy

[nate (Nathan)]

Thanks for the description of the problem guys.

Thanks,
Nate

[tommy (Tommy Gaessler)]

Happy to help!

I will post back here with updates.

Thanks,
Tommy

[vijayk.kannan (Vijay)]

here is the app id : sl6ZtUrdRma0PV912CiFSw

All our apps were affected , when will be fixed ?

[saro]

As of an hour or so ago it seems that our applications are firing the meeting.participant_left event correctly.

[tommy (Tommy Gaessler)]

Hey @saro, @vijayk.kannan, @nate,

The issue has been fixed. Apologies this happened.

Thanks,
Tommy

[nate (Nathan)]

Hi Tommy,

I am glad you guys were able to get this back up and running quickly.

Thanks,
Nate

[tommy (Tommy Gaessler)]

Happy to help!

-Tommy