@tommy Yes, it’s still happening consistently. Just tried it a minute ago.
Can you give me exact steps to reproduce?
- What app type? (Account/User Level OAuth or JWT)
- What type of meeting? (Recurring, scheduled, instant)
- When are you deleting it? (Before, During, or After meeting has started)
- OAuth app type.
- Scheduled meeting type.
- Deletion before meeting has started.
Thank you @ron.straight.
This may be due to your account being a Basic account.
To use the Zoom APIs you need at least a Pro account. Or you can request a Free Trail account to use/test the Zoom APIs.
Let me know how you want to move forward.
You mention a trial account, but I assume that’s only for testing, right? If we actually want to create an app that other users can use, it has to be owned by at least a Pro account?
A free trail account can create and publish apps to the Marketplace for as long as the free trail period.
If you want your App to work long term yes, I would suggest upgrading to the Pro Account.
Does that make sense?
I wouldn’t say it makes sense, but I understand what you’re saying.
It will at least be easier to test OAuth with users under our account.
@tommy Still getting that 500 when performing a DELETE on a meeting after upgrading to a Pro account. The deletion happens, but the response indicates otherwise.
This does seem like a bug. Can you give me a few of your meeting ID’s where you saw the 500 error so I can look at the logs?
I just deleted 226213781 and 370927595 a few minutes ago.
We will look at the logs and see what’s going on.
Will post back here with updates. ZOOM-110814
Update, this may be related to moving a Personal Zoom Account to a Sub Account under a Master Account.
We are looking into this edge case and will fix.
@tommy, after recreating the app, I’m still getting 500 on DELETE. Same behavior as before. The meeting is deleted, but the response has a status 500.
Just deleted 931674664 and 964129786.
Thanks for the update @ron.straight
Can you send me a screenshot of your App’s request logs in the Zoom App Marketplace Dashboard after you get the 500 error?
I didn’t know about that page. Very useful!
As you can see, it says it returned a 204. That makes me wonder if maybe the error is from our proxy. I don’t even see the DELETE calls in our logs, and checking the code shows we may not be handling an empty response body correctly.
I’ll let you know if I find anything contrary, but for now I think we can assume this is on our end.
Sorry for wasting your time. I’ll know to check the API logs next time before I go crying wolf.
No apology necessary! Happy to help!
Let us know if the issue is with your proxy or not.
It was definitely on our end. We’ve got a fix in for it now. Thanks again.
You are welcome!