Webhook events not triggering to our URL

Our system depends on Zoom webhook triggers. Everything was working just fine! All of a sudden, it stopped working; that means Zoom is no longer triggering our subscribed webhook events. The URL is validated, I’ve re-added the events, and it was validated and not sending events to our server.

I’ve tried every possible debugging but it seems like the issue is not with our services but completely with Zoom’s services themselves.

I shouldn’t disclose any of the information publicly, right? Looking for Zoom’s support so we can continue with more details.

@mahbub.meh for changes to webhook url in production, you will need to resubmit before it will take into effect.

For beta testing in production, you can regenerate the authorization URL for the webhook url to be updated and take into effect. If this is not the case, let me know again.

  1. It was just working perfectly fine; webhooks were coming. Suddenly, it stopped triggering the webhook when I didn’t make any changes*. even If I change the previous setting should work right? which means the previous webhook trigger should execute as it is.
  2. Even in ‘development’ mode, I tried it didn’t trigger(definitely, I’ve generated and used the fresh authorization URL)
  3. I’m completely clueless at this moment.

@chunsiong.zoom So, what do we do about it?

@mahbub.meh are you subscribing to cloud recording transcript completed event? You have triggered the cloud recording in your meeting?

Yes @chunsiong.zoom . I subscribed on recording.completed webhook + I was testing with cloud recording. the recording is showing on /recordings endpoint of zoom.

@mahbub.meh your account is a free account right? is there cloud recording enabled on this free account?

@chunsiong.zoom My account is free, right. But my employer account is paid, which I use to test the integration and all that. The webhook has never triggered since then! This is pretty weird.

I had the same thing happen recently. I had deployed new code and the webhook in production just stopped all of a sudden. I hadn’t changed the marketplace URL or anything like that.
My assumption is that during my deploy the URL for webhooks may have been down for a brief time. It seems like if Zoom calls a webhook endpoint and it doesn’t respond it will mark it as bad and not send to that URL again.
There is no visibility into this situation. I ended up going into my production app and changing the URL and then changing it back and revalidating. It started working again but that seems like a painful process. It would be nice if there was a way to tell Zoom to remove the “bad” URLs from its list and try the configured URL again.

@mahbub.meh let me get back to you in a bit.

I’m raising a request for this issue.

ZSEE-210674

We also have same issue. It has been working fine as expected for a long time. But recently we noticed that some webhooks are not being delivered. And these missing webhooks are not consistent also, some events for a meeting are received successfully, while other expected events for the same meeting are never received.

@remyapn please create a new thread instead of reply to this specific thread, and tag me there

@Canary_Speech the validation has to fail 7 consecutive times over a period of 7 days before it is invalidated,

You should be able to activate it just by re-validating it. If this process of revalidation is not working, tag me.

@chunsiong.zoom I was supposed to hear back faster! no response at all.

@mahbub.meh if you need a faster response with SLA, please sign up for premium developer support.

The support over developer forum is best effort. Nevertheless we will try to response as soon as possible.

Backend team is requesting for you to re-add the app to try again.

@chunsiong.zoom That’s completely fine. Thank you.

I was just trying to follow up on the case, as you said will be back with updates shortly.

I’ve already re-added it a few times to see, but it didn’t help.

Hey @chunsiong.zoom , I’ve re-added the app again with our software, but it seems not to be working even though.

I also tried adding a new route(link) for the webhook to bypass the caching-related stuff if there’s any. But still it didn’t work