# Event\_ts and breakout rooms

**URL:** <https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378>\
**Category:** API and Webhooks\
**Created:** [April 6, 2021, 7:51pm UTC](https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378 "2021-04-06T19:51:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidbalbert](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/davidbalbert/32/25549_2.png) [@davidbalbert](https://devforum.zoom.us/u/davidbalbert)\
**Post date:** [April 6, 2021, 7:51pm UTC](https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378/1 "2021-04-06T19:51:23Z")

</div>

**Description**

When we get meeting.participant\_left and meeting.participant\_joined webhooks for a given participant, we store the `leave_time` or `join_time` attribute to make sure we don’t process future webhooks out of order (if we receive a webhook that happened earlier than our stored time, we ignore it). Could we use [`event_ts`](https://marketplace.zoom.us/docs/api-reference/webhook-reference#delivery-latency) for this instead? In other words, does sorting a series of webhooks by `event_ts` guarantee you the same ordering as if you were to sort them by `join_time` and `leave_time`?

The reason I ask is because when a participant joins a breakout room, we get a meeting.participant\_left event and a meeting.participant\_joined event with identical `leave_time` and `join_time` attributes, breaking our previous method. We noticed that the `event_ts` timestamps are different (and higher resolution), and in the few examples we’ve seen, the order is always correct (the `event_ts` for the leave event is before the `event_ts` of the join event). I want to know if this will always be the case.

**Error**  
N/A

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

**Which Endpoint/s?**  
meeting.participant\_left  
meeting.participant\_joined

**How To Reproduce (If applicable)**  
Steps to reproduce the behavior:

1. Join a breakout room
2. Observe the webhooks delivered

---

<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:** [April 7, 2021, 3:32pm UTC](https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378/2 "2021-04-07T15:32:35Z")

</div>

Hey @davidbalbert,

Thanks for reaching out about this, and good question.

I don’t see any issues with using the event\_ts timestamp for this purpose. As you mentioned, this will reflect the exact timestamp of when the associated event occurred. If you’re trying to account for the same timestamps when participants leave a breakout room and rejoin a main meeting, I think this approach should work for you.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![davidbalbert](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/davidbalbert/32/25549_2.png) [@davidbalbert](https://devforum.zoom.us/u/davidbalbert)\
**Post date:** [April 7, 2021, 4:02pm UTC](https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378/3 "2021-04-07T16:02:00Z")

</div>

Thanks so much @will.zoom. That’s very helpful.

---

<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:** [April 7, 2021, 4:39pm UTC](https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378/4 "2021-04-07T16:39:08Z")

</div>

No problem, glad I could help!

---

<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:** [May 8, 2021, 2:40am UTC](https://devforum.zoom.us/t/event-ts-and-breakout-rooms/47378/5 "2021-05-08T02:40:02Z")

</div>

Closed on May 8, 2021, 2:40am UTC

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