Cannot delete location scope error 4711 (empty array)

API and Webhooks
22

Here are a few new tracking Ids:

x-zm-trackingid: v=2.0;clid=us06;rid=WEB_7f89857113e0d49584efb3817663b600
x-zm-trackingid: v=2.0;clid=us06;rid=WEB_68cb59d300ec8da15500a970b1f7cec6
x-zm-trackingid: v=2.0;clid=us06;rid=WEB_e703fb35cb957d923f7b5506aab4f750
x-zm-trackingid: v=2.0;clid=us06;rid=WEB_e7880ded4ab45b2a09447114c5e0c138
23

Thanks so much, looking into it.

1 Like
24

Still waiting to hear from service engineering team. I just followed up with them. Thanks for your patience.

25

Hi @desautelsj so this is definitely a bug with the granular scope (ZOOM-940063). Release date for fix not shared yet. Thanks for following up on this!

26

Great I’m glad we got to the bottom of it.

I’m baffled by the fact that you were not able reproduce in your testing though. Any insight why you didn’t get the error while @thomas.leguen and I did?

27

Hi @desautelsj , I was using the legacy scope as opposed to granular one

28

Hi @desautelsj this should be resolved in the upcoming May release.

29

Excellent, thanks for following up.

30

@desautelsj No problem! Thanks for your investigation. After May changelog release, can you please confirm in this thread when you’ve checked again?

31

I have been monitoring the changelog and I haven’t seen any mention of changes related to deleting room locations but, out of curiosity, I attempted to delete a location and I am now getting a different result:

REQUEST:
DELETE https://api.zoom.us/v2/rooms/locations/m8zgreeDSre0gppeSgIppg

RESPONSE:
HTTP/1.1 400 Bad Request
{"code":200,"message":"Access restricted."}

The tracking ID, in case it’s helpful, was:

x-zm-trackingid: v=2.0;clid=us06;rid=WEB_d8dba1806b4e8d7042d3ab74ddbb8f37
32

@desautelsj okay I’m checking with the team.

33

I think I figured it out. There was a room associated with the location I was attempting to delete. I manually deleted the room and ran my “delete a location” API test again: it completed successfully.

So, this latest problem was simply a misleading error message: the problem had noting to do with permissions, scopes, access being denied or anything like that. It would have been helpful if the message was more explicit. Something along the lines of You can not delete this location because a room is associated with it.

Long story short: the issue with the “delete location” API end point seems to have been fixed. It’s weird that this fix wasn’t mentioned in the Zoom Developer Changelog.

1 Like
34

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