# Meeting Update API - PATCH - Bug in disable auto\_recording settings update

**URL:** <https://devforum.zoom.us/t/meeting-update-api-patch-bug-in-disable-auto-recording-settings-update/115804>\
**Category:** API and Webhooks\
**Tags:** api\
**Created:** [August 17, 2024, 7:11am UTC](https://devforum.zoom.us/t/meeting-update-api-patch-bug-in-disable-auto-recording-settings-update/115804 "2024-08-17T07:11:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahesh.mahadevan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mahesh.mahadevan/32/47533_2.png) [@mahesh.mahadevan](https://devforum.zoom.us/u/mahesh.mahadevan)\
**Post date:** [August 17, 2024, 7:11am UTC](https://devforum.zoom.us/t/meeting-update-api-patch-bug-in-disable-auto-recording-settings-update/115804/1 "2024-08-17T07:11:37Z")

</div>

**API Endpoint(s) - Zoom Meeting Update a Meeting**  
_Link - [Zoom Meeting API](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/meetingUpdate)_

**Description**  
There is a bug when we try to update `auto_recording` settings on the meeting using the above PATCH call , it responds back with success `HTTP 204` to be precise but when we fetch the meeting again using the GET call, the actual settings has not been updated correctly. This seems to be happening for the following request body

```auto
{'settings': {'auto_recording': "none"}}

```

Whereas , the change to changing the start time seems to be working fine , so there is no issue with scopes here.

**Error?**  
There are no errors but the PATCH update does not take effect.

**How To Reproduce**  
_Steps to reproduce the behavior:_  
Use the following code

```auto
import requests
request_body = {'settings': {'auto_recording': "none"}}
zoom_meeting_id = "123456"
MEETINGS_URL = "https://api.zoom.us/v2/meetings/"
resp = requests.patch(
    MEETINGS_URL + str(zoom_meeting_id),
    headers={'Authorization': 'Bearer ' + <ACCESS_TOKEN>},
    json=request_body,
)

print(resp.status_code)

# Get the same meeting
resp = requests.get(
    MEETINGS_URL + str(zoom_meeting_id),
    headers={'Authorization': 'Bearer ' + <ACCESS_TOKEN>},
)
print(resp.json())

```

---

<div class="post-metadata">

**Author:** ![mahesh.mahadevan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mahesh.mahadevan/32/47533_2.png) [@mahesh.mahadevan](https://devforum.zoom.us/u/mahesh.mahadevan)\
**Post date:** [August 19, 2024, 9:52am UTC](https://devforum.zoom.us/t/meeting-update-api-patch-bug-in-disable-auto-recording-settings-update/115804/2 "2024-08-19T09:52:45Z")

</div>

Found the root cause , this was due to locking of Auto Recording settings in Zoom Account Settings.

 ![Screenshot 2024-08-19 at 12.18.06 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/f/0/f06170889c0eff13daca12fdf5e495766a3a5cfa.png)

My request to zoom team is to try and update the responses and errors during such scenarios as it makes debugging difficult when the responses are success but the actual change does not take effect.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [August 26, 2024, 4:50pm UTC](https://devforum.zoom.us/t/meeting-update-api-patch-bug-in-disable-auto-recording-settings-update/115804/3 "2024-08-26T16:50:06Z")

</div>

@mahesh.mahadevan Thanks for sharing your findings with the community!

---

<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:** [August 27, 2024, 4:50pm UTC](https://devforum.zoom.us/t/meeting-update-api-patch-bug-in-disable-auto-recording-settings-update/115804/4 "2024-08-27T16:50:31Z")

</div>

Closed on August 27, 2024, 4:50pm UTC

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