Webhook inconsistency

Description
Webhooks are inconsistent in firing of events.

Im using Zoom Room Alert event and sometimes the event for room offline is not firing.

Are there any limits for webhooks events?

I also notice that in my zoom account there is a page in were one can see the webhooks being fired but i could not see any of the webhooks being fired… (https://marketplace.zoom.us/user/logs?type=WebhookOnly)

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

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

Which Endpoint/s?
Zoom Room Alert

Hey @mackie,

Right now, you will only see the logs on that page if you are using a Webhook-only app type. Feel free to set one up so you can see the logs.

Can you confirm you are sending a 200 OK response after receiving a webhook?

Thanks,
Tommy

Hi tommy,

Yes I am sending a 200 ok response.

router.post(’/zoom’, async function(req, res) {
let event = { …req.body };

console.log(‘’);
console.log(‘ZOOM WEBHOOK EVENT:’, event);
console.log('
’);

res.send(JSON.stringify({ status: 200, error: null, response: event }));
});

I updated my app type to weebhook only…

Thanks,
Mackie

Hi Tommy,

I can now see the webhook calls in the webhook logs page but unfortunately there are inconsistencies with the webhook room alerts. There are times room offline and online are fired and there are times they are not fired.

Can you please let me know what are the constraints from webhook room alert not being fired? Currently we are just turning off the computer where the zoom room is installed. We want to know if the room is offline or not using the webhook…

Thanks,
Mackie

Hey @mackie,

Can you share the Zoom Room ID with me so I can have our engineering team debug?

Thanks,
Tommy

Hi Tommy,

{
“id”: “9z1JGrfBSkqO-ftt-YJxpw”,
“name”: “Cebu Huddle Room”,
“room_id”: “XWjcCAzmT0OIc893wHPvtQ”,
“status”: “Available”
}

Thanks,
Mackie

Thanks for the info @mackie!

Our engineering team is looking into the issue. (ZOOM-172037)

-Tommy

Hey @mackie,

We have confirmed this is a bug, and are working to fix it as soon as possible.

Thanks,
Tommy

Hello @tommy,

What is the status for this bug? How can I know if this bug is fix?

Thanks,
Mackie

Hey @mackie,

We are currently working on the fix. I will keep you updated in this thread on the timeline.

Thanks,
Tommy

Hey @mackie,

We will be fixing this bug in August.

Thanks,
Tommy

Hi @tommy,

Was the fix already been deployed?

Thanks,
Mackie

Hey @mackie,

Yes, this has been deployed! :slight_smile:

Are you still seeing the issue?

Thanks,
Tommy