# Webhook call not receiving for cloud recording **URL:** \ **Category:** Cloud Recordings\ **Tags:** webhooks, recording\ **Created:** [March 22, 2023, 5:32am UTC](https://devforum.zoom.us/t/webhook-call-not-receiving-for-cloud-recording/85122 "2023-03-22T05:32:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![learning2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/learning2/32/46683_2.png) [@learning2](https://devforum.zoom.us/u/learning2)\ **Post date:** [March 22, 2023, 5:32am UTC](https://devforum.zoom.us/t/webhook-call-not-receiving-for-cloud-recording/85122/1 "2023-03-22T05:32:57Z")
* * * **Zoom Webhook Event(s)** _recording.completed & recording.started webhook call._ **Description** _The problem we are fetching with recording related webhook calls. That problem we are getting for subaccounts. I have one main account (Pro account) and two subaccount. So, for main account, the recording webhook calls are receiving to our system. But, in case of subaccounts, we are not getting only recording related webhook calls from zoom side. We are receiving meeting related webhook calls like **meeting.started** and **meeting.ended** for subaccounts also from the zoom._ **Error?** _Not getting any error, we have checked on webhook logs also. But, in webhook logs, there are no records for recording related webhook events for subaccounts._ ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [March 23, 2023, 1:07am UTC](https://devforum.zoom.us/t/webhook-call-not-receiving-for-cloud-recording/85122/2 "2023-03-23T01:07:23Z")
@learning2 , sorry you are experiencing this. Please see this guidance: > [@Guide: "We Are Not Receiving Webhooks As Expected" -- Here's What to Do!](https://devforum.zoom.us/t/we-are-not-receiving-webhooks-as-expected-heres-what-to-do/64846): > > Please reference this post first: [https://zoomdevelopersupport.zendesk.com/hc/en-us/articles/360054379371-Not-receiving-Webhooks](https://zoomdevelopersupport.zendesk.com/hc/en-us/articles/360054379371-Not-receiving-Webhooks) If this does not resolve the matter, open up a [support ticket](https://devsupport.zoom.us/hc/en-us) with the following: affected webhook types affected meeting and/or participant Id(s) account Id notification endpoint url(s) where webhooks are sent time frame of affected instances steps to reproduce screenshots of errors (if applicable) Thank you! ---
**Author:** ![learning2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/learning2/32/46683_2.png) [@learning2](https://devforum.zoom.us/u/learning2)\ **Post date:** [March 23, 2023, 6:01am UTC](https://devforum.zoom.us/t/webhook-call-not-receiving-for-cloud-recording/85122/4 "2023-03-23T06:01:08Z")
@gianni.zoom I have refer the above post that you have mentioned and the step mentioned on the post that I have already setup. But, still clould recording webhooks are not receiving for sub accounts. And I am using pro plan. I have raised the ticket also. But, not getting any solution. Support Ticket : [https://support.zoom.us/hc/en-us/requests/16841005](https://support.zoom.us/hc/en-us/requests/16841005) ---
**Author:** ![rachelgomez161999](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rachelgomez161999/32/35985_2.png) [@rachelgomez161999](https://devforum.zoom.us/u/rachelgomez161999)\ **Post date:** [March 27, 2023, 7:16am UTC](https://devforum.zoom.us/t/webhook-call-not-receiving-for-cloud-recording/85122/5 "2023-03-27T07:16:33Z")
To manage failed messages, Commerce monitors each target URL that a webhook is configured to send messages to, and if a URL is unresponsive, disables it as a target. For example, if the Order Submit webhook sends messages to three different URLs, and Commerce detects that calls to one of the URLs are failing consistently (returning non-200-level status codes, or not returning any response), it stops sending messages to this URL, while continuing to send messages to the other two URLs. The messages for the disabled URL are instead added directly to the failed message log. Commerce continues monitoring the disabled target. When it detects that the URL is responding again, it resumes sending messages to it. Messages to the URL that failed previously (either reached the maximum number of retries, or were sent directly to the failed message log after Commerce disabled the target) are queued for resending. Note that it may take a while for all failed messages to be resent. Regards, Rachel Gomez