Hi @tommy ,
Is there anyway we can mitigate this issue?
This is creating invalid status in meeting for us.
So if attendee joined and left and joined again, due to unordered events, status is showing as left but actually he is in meeting.
Is there anyway we can handle it at our end.
tommy
(Tommy Gaessler)
August 31, 2020, 4:01pm
22
Hey @taushifali ,
This issue should not be common. How often are you seeing this?
You can always validate participant info via the Participant Reports endpoint:
Thanks,
Tommy
Hi @tommy ,
Another issue in meeting hooks, not receiving meeting_id in the payload, it is coming as null. Object.id is meeting_id which is null in this case, why this is coming as null, how can we identify meeting_id in such case?
{“payload”:{“account_id”:“WxALpvKiQ0K-mPH3AxL6aw”,“object{“uuid”:“P6eYaYvCSJmWzppVS6wbWg==”,“participant”:{“user_id”:“16778240”,“user_name”:“Furkan ali”,“id”:”",“join_time”:“2020-09-08T15:28:47Z”},“id”:null,“type”:0,“topic”:null,“host_id”:"",“duration”:0,“start_time”:null,“timezone”:null}},“event”:“meeting.participant_joined”}
will.zoom
(Will)
September 10, 2020, 5:33pm
24
Hi @taushifali ,
Thanks for bringing this example to our attention—this is something our team is actively looking into. (ZOOM-147866).
I’ll let you know as soon as I have an update.
Best,
Will
system
(system)
Closed
September 20, 2020, 5:33pm
25
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.