Using this template helps us debug your issues more effectively
Description
The webhook received on the event meeting.participant_left
the value for participant email: ```
“22058\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000”,
which brought up an error on my server.
The weirdest part is that it was the host's email -- and I know the hosts email as we have programmatically created the zoom_meeting with a known email
**Which App Type (OAuth / Chatbot / JWT / Webhook)?**
Webhook
**Which Endpoint/s?**
Particant_left
**How To Reproduce (If applicable)**
I couldn't reproduce it yet
Thank you for reaching out to the Zoom Developer Forum. Just to make sure I understand, you saw that the email for a participant used that value but this was the only instance you’ve seen. Have you had that participant attempt to join a meeting again to see if you see the same problem?
I would also test with a tool like Request Bin to ensure that any issues you’re seeing aren’t related to the logic of the endpoint.
Hey @MaxM,
It happened again today. It happened to a participant who happened to be an employee of our company, and who used a known employee email.
This type the email sent by the api was 654-885100778622\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
Thank you for providing more information. Just to clarify, this participant joined via the Zoom Client is that correct? If so, I would make sure they are using the latest version of the Zoom Client and then test to see if that issue persists.
Thank you for your patience. Our engineering team is still looking into this issue but this seems to be related to a bug with the DB cache. I’ll keep you posted with any new information.
The error happened again 3 times yesterday, and it is now affecting another Zoom account (user_id: [REDACTED]). Let me know if we can provide your engineering team with more information to help debugging
Thank you for sending that my way. No news from our engineering team just yet but I see activity on the ticket and I’ll forward this new value to them as well.