{"code":3301,"message":"This recording does not exist."}

[RVChandan3]

I am developer in edtech company. our company provide support for online classes to tutors and learners by zoom. I can see captured events log for a meeting that has recording started/stopped events. but fetchRecordingAPI is giving response code 3301 with message The recording does not exist.
the meeting happened on 21st may and user's doesn't have access to delete/update. 
Is there any possibility to get the recording back from zoom side.

[RVChandan3]

@zoom  can i get any support here?

[TT92]

Hi,

I’m running into a similar issue: I receive the 3301 error message when trying to fetch recordings. The trigger I’m using is when the transcript is finished so the recording is present... Also, when I log into Zoom on the web, I can clearly see that the recording is present.

Some extra details:

• I’m an admin account.

• The user involved does not have permissions to delete or update recordings.

• It doesn’t happen every time — more like 1 out of every 10–15 recordings triggers this issue.

I tried to contact directly to @zoom dev support but unfortunately they send me to the community as i need to have payed support for this request... 

[MGSR]

Hello there,

We're sorry for the inconvenience you experienced. 

You can check out this article for the Zoom error message "This recording does not exist. (3301). 

Let us know if this helps or if you need further assistance.

[TT92]

Hi Mark,

Thanks for your reply.

I already went through that article, but as mentioned in my original post the error only occurs sporadically. When it happens, I can still see the recording in Zoom, it has not been deleted or moved to the trash.

Do you have any idea what could cause this inconsistency?

[TT92]

Hi Mark,

Two days ago, it happened again — we received another 3301 error message.

The recording is still fully visible in the admin panel (Account Management → Recording and Transcript Management), but the API fails to fetch it.

As before, most attempts succeed (20+ in a row), but then sporadically 1 or 2 fail.

See attached pictures.

Hopefully you and your team could have a look into this issue.