Description
Users who join the waiting room prior to a meeting having started seem to frequently be generating duplicate meeting.participant_jbh_waiting events via the Webhook. The duplicate events are usually 30-35 seconds apart from each other.
Which App Type (OAuth / Chatbot / JWT / Webhook)?
This message is coming from a webhook tied to event type meeting.participant_jbh_waiting.
We’ve verified that the only response we’re ever returning via the webhook endpoint is a 200 OK (even if there’s an error parsing the JSON).
What’s odd is that this only seems to be happening with meeting.participant_jbh_waiting events. No other event type is doing this. They are all spaced out 30-35 seconds from each other.
We ended up putting some code in place that compares the incoming JSON to anything that’s already been logged and are skipping the logging if it’s a duplicate, but that comes with some overhead.
If you’d like a few examples of duplicates from this morning, here are some meeting IDs:
*********** (sent 15 times today)
*********** (sent 63 times today)
~Justin
*This post has been edited to remove any meeting / webinar IDs
It’s seems relatively common for the user_name to come across without a value. In the past hour, 37 of the 150 events we logged with a status of meeting.participant_jbh_waiting had a blank participant { user_name }.
In these cases, the user is being redirected to the Join_URL link. We’re not exactly clear what device(s) the users might be using, it’s probably a mixture of mobile devices and desktop devices. These are end-users (public, not associated with our account) joining meetings that we’ve set up, configured to place them into the waiting room if the meeting hasn’t started yet.
I personally have been unable to replicate the missing username - when I join the same link from my phone, it appears to pass my phone’s name into the WebHook data. I’m using iOS.