# Webhook Request Simultaneously Executed

**URL:** <https://community.hubspot.com/t/webhook-request-simultaneously-executed/11711>\
**Category:** APIs & Integrations\
**Tags:** contacts\
**Created:** [September 28, 2018, 7:36pm UTC](https://community.hubspot.com/t/webhook-request-simultaneously-executed/11711 "2018-09-28T19:36:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [September 28, 2018, 7:36pm UTC](https://community.hubspot.com/t/webhook-request-simultaneously-executed/11711/1 "2018-09-28T19:36:32Z")

</div>

I have a Webhook attached to add contacts, with property changes for form submissions and phone.  
It happens el lot that, for example, there’s a trigger for the form submission, and that submission changes the phoen too, so both protery changes occurs almost at the same time, sending both request at almost the same time.  
The problem is that, the subscribed part receives this and sometimes duplicates the information, since it occurs wihitin miliseconds of difference.  
I saw that you can configure simultaneus requests, but the minimun is 5, so that’s not an option.

[![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/9/6/96c4fbc49ac88f00792a411d3dbfacc0968ecc68.png)

image.png2179x259 18.1 KB

]([https://community.hubspot.com/legacyfs/online/uploads/default/original/2X/6/61a5a7dfaad9bbab638eb156683ed1b3d651a184.png](https://community.hubspot.com/legacyfs/online/uploads/default/original/2X/6/61a5a7dfaad9bbab638eb156683ed1b3d651a184.png))

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [October 2, 2018, 2:10pm UTC](https://community.hubspot.com/t/webhook-request-simultaneously-executed/11711/2 "2018-10-02T14:10:13Z")

</div>

Hi [@dquagliano](https://community.hubspot.com/u/dquagliano),

Could you clarify your goal?

The behavior you have described is normal if you have opted to subscribe to receive notifications when a contact is created and when a contact’s phone number property change. If a creation event also updates the phone number, then you should receive two different notifications, as your screenshot shows.

Similarly, [this documentation](https://developers.hubspot.com/docs/methods/webhooks/webhooks-overview) notes:

> We do not guarantee that you will only get a single notification for an event. Though this should be rare, it is possible that we will send you the same notification multiple times.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 2, 2018, 8:12pm UTC](https://community.hubspot.com/t/webhook-request-simultaneously-executed/11711/3 "2018-10-02T20:12:13Z")

</div>

Hi [@Isaac\_Takushi](https://community.hubspot.com/u/isaac_takushi),  
I’m aware that this is how it’s expected to work, that’s why I was asking for any possible workaround.  
I wasn’t aware about that documentation text, so I guess that lowers the possibilities to have a workaround.

More clarification about the goal:  
The subscriber receives both request simultaneously, and I don’t have much control over that endpoint, so sometimes it will duplicate data on the other end, since both request will be generating it at the same moment, the validation of duplicate data won’t trigger.

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [October 5, 2018, 1:13pm UTC](https://community.hubspot.com/t/webhook-request-simultaneously-executed/11711/4 "2018-10-05T13:13:44Z")

</div>

Thank you for clarifying, [@dquagliano](https://community.hubspot.com/u/dquagliano). I haven’t found any workarounds on our end, though.

For context, [this similar topic](https://integrate.hubspot.com/t/single-event-triggering-multiple-notifications/8564) covers notification uniqueness in a bit more detail. As Derek notes, HubSpot considers notifications with identical `eventId` _and_ `subscriptionid` values duplicates.