# Webhook with id object.id=null

**URL:** <https://devforum.zoom.us/t/webhook-with-id-object-id-null/9214>\
**Category:** API and Webhooks\
**Created:** [March 22, 2020, 11:36am UTC](https://devforum.zoom.us/t/webhook-with-id-object-id-null/9214 "2020-03-22T11:36:58Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![alon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/alon/32/3471_2.png) [@alon](https://devforum.zoom.us/u/alon)\
**Post date:** [March 29, 2020, 12:16pm UTC](https://devforum.zoom.us/t/webhook-with-id-object-id-null/9214/6 "2020-03-29T12:16:15Z")

</div>

I’m guessing this is an issue of some job worker communicating with a replication DB which is not synced yet, hence it does not find the meeting object.  
Is it reasonable to think that if I fail the webhook with 500, the next retry will contain the meeting id? Or is the retry mechanism separated and the same event JSON will be sent anyways?

---

_[View the full topic](https://devforum.zoom.us/t/webhook-with-id-object-id-null/9214)._
