# Duplicate status events from webhook **URL:** \ **Category:** Users and Groups\ **Tags:** webhooks\ **Created:** [February 28, 2023, 4:49pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873 "2023-02-28T16:49:57Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jonathan3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonathan3/32/45490_2.png) [@jonathan3](https://devforum.zoom.us/u/jonathan3)\ **Post date:** [February 28, 2023, 4:49pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873/1 "2023-02-28T16:49:57Z")
### Topic Duplicate event coming in several minutes after initial status event. **Description** As seen in the data below, we are receiving a duplicate event several minutes after it occurs, as shown by the matching timestamps with the created date in EST. Is this expected, possibly from two different devices? Is another event supposed to be coming in? **Example** | Email | Status | Timestamp | created date | | --- | --- | --- | --- | | a.s@ch. com | Available | 1677601666891 | 2023-02-28 11:32:50.091 -0500 | | a.s@ch. com | Available | 1677601666891 | 2023-02-28 11:27:46.937 -0500 | | a.s@ch. com | Offline | 1677601508847 | 2023-02-28 11:30:13.023 -0500 | | a.s@ch. com | Offline | 1677601508847 | 2023-02-28 11:25:08.926 -0500 | ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [March 1, 2023, 4:25pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873/2 "2023-03-01T16:25:42Z")
Hi @jonathan3 Thanks for reaching out to us! I do not think this is expected. Could you confirm what events are you listening to? ---
**Author:** ![jonathan3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonathan3/32/45490_2.png) [@jonathan3](https://devforum.zoom.us/u/jonathan3)\ **Post date:** [March 1, 2023, 7:07pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873/3 "2023-03-01T19:07:17Z")
We are currently listening to the following status events **User has signed in** **User has signed out** **User’s presence status has been updated** and to note, We do have another webhook in the same app with phone events, pointing to a different endpoint. ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [March 1, 2023, 7:16pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873/4 "2023-03-01T19:16:56Z")
Hey @jonathan3 Do you think that the user might be updating the status or signing in and out and that’s why you are getting duplicate events??? I will go ahead and do some testing on my end and will come back to you with an update Cheers, Elisa ---
**Author:** ![jonathan3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonathan3/32/45490_2.png) [@jonathan3](https://devforum.zoom.us/u/jonathan3)\ **Post date:** [March 2, 2023, 1:27pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873/5 "2023-03-02T13:27:55Z")
I would be hesitant to say its the user signing in / out because of the matching timestamps. The timestamp field in column three is the event\_ts that is coming through the webhook, while the created\_date field is when it was added to the database. With the same event timestamp, it seems like it is sending the same event twice. From a user perspective, it could be coming from one device registering the status change on a separate device (like a phone and computer), and then sending out the status change with the same time stamp as the original status change? ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [March 3, 2023, 3:10pm UTC](https://devforum.zoom.us/t/duplicate-status-events-from-webhook/83873/6 "2023-03-03T15:10:53Z")
Thanks @jonathan3 I will send you a private message to follow up