# Recording started callback **URL:** \ **Category:** Meeting SDK\ **Created:** [July 15, 2020, 7:11pm UTC](https://devforum.zoom.us/t/recording-started-callback/24227 "2020-07-15T19:11:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vinay](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay/32/11954_2.png) [@vinay](https://devforum.zoom.us/u/vinay)\ **Post date:** [July 15, 2020, 7:11pm UTC](https://devforum.zoom.us/t/recording-started-callback/24227/1 "2020-07-15T19:11:18Z")
Is it possible to setup a “cloud recording started” callback from the electron (or Mac) SDK? I would like to trigger a notification in my app when cloud recording starts. ---
**Author:** ![carson.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/carson.zoom/32/785_2.png) [@carson.zoom](https://devforum.zoom.us/u/carson.zoom)\ **Post date:** [July 16, 2020, 6:58am UTC](https://devforum.zoom.us/t/recording-started-callback/24227/2 "2020-07-16T06:58:07Z")
Hi @vinay, Thanks for using Zoom SDK. I will forward this as a feature request to the engineering team. One alternative solution at the moment would be the Webhook:[https://marketplace.zoom.us/docs/api-reference/webhook-reference/recording-events/recording-started](https://marketplace.zoom.us/docs/api-reference/webhook-reference/recording-events/recording-started) Thanks! ---
**Author:** ![vinay](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay/32/11954_2.png) [@vinay](https://devforum.zoom.us/u/vinay)\ **Post date:** [July 16, 2020, 5:48pm UTC](https://devforum.zoom.us/t/recording-started-callback/24227/3 "2020-07-16T17:48:53Z")
@carson.zoom – thanks for the quick response. I think I’ve successfully integrated the `startCloudRecording`, `stopCloudRecording`, and `canStartRecording` methods from the [native mac SDK](https://github.com/zoom/zoom-sdk-macos/blob/97f88065d376dc4c4774a655b9bb060b0c6a3214/ZoomSDK/ZoomSDK.framework/Versions/A/Headers/ZoomSDKMeetingRecordController.h#L153) into the electron SDK. When I use them in the demo app, I get `ZNSDK_SUCCESS` from `canStartRecording(true)` but `12` from `stopCloudRecording` (while my meeting is recording). 12 does not seem to be one of the values in [ZoomSDKErrors](https://github.com/zoom/zoom-sdk-electron/blob/dbdff5a65dff40c1bccb7a1b269391ea72d8f6b5/sdk/mac/ZoomSDK/ZoomSDK.framework/Versions/A/Headers/ZoomSDKErrors.h#L232-L260). In `ZNSDKError` it’s `ZNSDKERR_NO_PERMISSION`. added: definitely a “no permission error” ---
**Author:** ![carson.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/carson.zoom/32/785_2.png) [@carson.zoom](https://devforum.zoom.us/u/carson.zoom)\ **Post date:** [July 18, 2020, 12:55am UTC](https://devforum.zoom.us/t/recording-started-callback/24227/4 "2020-07-18T00:55:06Z")
Hi @vinay, Thanks for the reply. Could you provide an SDK log for us to further investigate? You could set true to `enable_log` when you use `setDomain` and if you are using Mac, you will find the SDK log in `~/Library/Logs/DiagnosticReports/(appName)` Thanks! ---
**Author:** ![vinay](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vinay/32/11954_2.png) [@vinay](https://devforum.zoom.us/u/vinay)\ **Post date:** [July 20, 2020, 2:01pm UTC](https://devforum.zoom.us/t/recording-started-callback/24227/5 "2020-07-20T14:01:03Z")
Here’s a log from this morning – this is what I did in the app: 1. Logged in with a ZAK token (Meetings default to recording on startup) 2. Clicked “stop cloud recording button” that I added (error 12) 3. Stopped recording from the Zoom UI 4. Clicked “start cloud recording button” that I added (error 12) [Electron.app\_0.log](https://drive.google.com/file/d/12_IOxx3tNNfGKkLt0zb-PB-HAHWF1ej3/view?usp=sharing) ---
**Author:** ![carson.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/carson.zoom/32/785_2.png) [@carson.zoom](https://devforum.zoom.us/u/carson.zoom)\ **Post date:** [July 23, 2020, 10:19pm UTC](https://devforum.zoom.us/t/recording-started-callback/24227/6 "2020-07-23T22:19:26Z")
Hi @vinay, Thanks for the information and the log. We are able to identify an issue based on the info provided and we will fix this in the next release. Thanks!