Bug: empty recording_files array returned in /users/me/recordings

After much time and painful debugging with a user of my app, I discovered that one of their cloud recordings returns with an empty “recording_files” array. My code wasn’t expecting that and so threw undefined exceptions later on.

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?

How To Reproduce (If applicable)
Meeting UUID: avUcDWTPTCmaG0KhWe/X7Q==

^ I’m assuming Zoom staff can work with that:

  1. Hit API for that user’s recordings.
  2. Find that meeting UUID.
  3. See the empty recording_files array.

Hi @nathanwaters,

Thank you for reaching out about this, and happy to take a closer look.

While the UUID is helpful, can you please also provide a copy of the payload you received as well?

This will help me to further investigate—thanks!


Thanks for sharing this, @nathanwaters.

In taking a closer look at the payload and meeting, I can see that this meeting was only a few seconds in duration. In order for recording files to be generated, the Meeting will need to have a longer duration. I would recommend ensuring the meeting is at least a minute in order for a recording file to be generated.

I hope this helps to clarify, but let me know if you still have questions.


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