# Report webinar participants with duration 0

**URL:** <https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934>\
**Category:** API and Webhooks\
**Created:** [November 13, 2020, 9:40am UTC](https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934 "2020-11-13T09:40:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![eso](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/eso/32/18722_2.png) [@eso](https://devforum.zoom.us/u/eso)\
**Post date:** [November 13, 2020, 9:40am UTC](https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934/1 "2020-11-13T09:40:02Z")

</div>

Our application relies on the duration of the attendance of participants to the webinars.  
After a webinar ends, we use the endpoint “/v2/report/webinars/{webinarId}/participants” to fetch all the participant durations.  
In some cases the reports shows duration=0 and joinTime=leaveTime (not for all participants, just some of them).

We experienced this behavour for a webinar scheduled yesterday (2020 13 11 at 05:30 PM +1:00) .  
If I call the same enpoint now, the duration and leaveTime are correct.

I see that the same issue was already reported here:

> [@Participants with duration 0 seconds](https://devforum.zoom.us/t/participants-with-duration-0-seconds/12892):
>
> My application fetches participants on webinar.ended event. Lots of participants have duration 0 and start time equal to leave time. Some time later, those participants do get valid duration, start\leave times. Is this expected behavior? If so, is there any way to determine when the participants data is complete?

Is there an amount of time we should wait to be sure that the report data are completely collected?  
Thank you

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [November 16, 2020, 6:16pm UTC](https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934/2 "2020-11-16T18:16:35Z")

</div>

Hi @eso,

It can take a little bit of time for a report to be processed after a meeting is ending. Are you currently attempting to fetch this report immediately following the meeting?

If so, I might recommend adding in a bit of buffer time—perhaps a minute or two, to give the report a little additional time.

Let me know if this helps,  
Will

---

<div class="post-metadata">

**Author:** ![eso](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/eso/32/18722_2.png) [@eso](https://devforum.zoom.us/u/eso)\
**Post date:** [November 18, 2020, 10:40am UTC](https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934/3 "2020-11-18T10:40:43Z")

</div>

Hi @will.zoom,  
thank you for your reply.  
I’m going to update our system in order to wait two minutes after the webinar has ended.

We have lot of webinars scheduled in the next weeks, so we will have the opportunity to check if this additional time is always enough to receive an up to date report.

Thank you  
Kind regards

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [November 18, 2020, 10:34pm UTC](https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934/4 "2020-11-18T22:34:59Z")

</div>

Hi @eso,

I think that’s a good idea, too! Hope this helps.

Best,  
Will

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [December 19, 2020, 8:35am UTC](https://devforum.zoom.us/t/report-webinar-participants-with-duration-0/35934/5 "2020-12-19T08:35:06Z")

</div>

Closed on December 19, 2020, 8:35am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
