# Duplicate webhooks received for recording completion in less than 5 seconds

**URL:** <https://devforum.zoom.us/t/duplicate-webhooks-received-for-recording-completion-in-less-than-5-seconds/101616>\
**Category:** API and Webhooks\
**Tags:** webhooks, api\
**Created:** [January 11, 2024, 7:42am UTC](https://devforum.zoom.us/t/duplicate-webhooks-received-for-recording-completion-in-less-than-5-seconds/101616 "2024-01-11T07:42:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ramchandra.am](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@ramchandra.am](https://devforum.zoom.us/u/ramchandra.am)\
**Post date:** [January 11, 2024, 7:42am UTC](https://devforum.zoom.us/t/duplicate-webhooks-received-for-recording-completion-in-less-than-5-seconds/101616/1 "2024-01-11T07:42:01Z")

</div>

For our webhook only app, we subscribe to recording completion events as a webhook call.  
We’re seeing multiple events, about 1-10 seconds apart consistently for this event after recording is completed.  
They arrive so close together it’s making it hard to manage them both.

For example, first received at 10:59:29.526  
Second arrives 10:59:30.537

This happens consistently for 40% of all the recordings.  
I’ve followed many other reports of this problem without any resolution.

Thank you

---

<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:** [January 13, 2025, 11:18pm UTC](https://devforum.zoom.us/t/duplicate-webhooks-received-for-recording-completion-in-less-than-5-seconds/101616/2 "2025-01-13T23:18:50Z")

</div>

Closed on January 13, 2025, 11:18pm UTC

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