# Bug: empty recording\_files array returned in /users/me/recordings

**URL:** <https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867>\
**Category:** API and Webhooks\
**Created:** [January 18, 2021, 12:17pm UTC](https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867 "2021-01-18T12:17:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nathanwaters](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nathanwaters/32/65443_2.png) [@nathanwaters](https://devforum.zoom.us/u/nathanwaters)\
**Post date:** [January 18, 2021, 12:17pm UTC](https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867/1 "2021-01-18T12:17:35Z")

</div>

**Description**  
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)?**  
OAuth

**Which Endpoint/s?**  
/users/me/recordings

**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.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [January 19, 2021, 8:34pm UTC](https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867/2 "2021-01-19T20:34:40Z")

</div>

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!  
Will

---

<div class="post-metadata">

**Author:** ![nathanwaters](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nathanwaters/32/65443_2.png) [@nathanwaters](https://devforum.zoom.us/u/nathanwaters)\
**Post date:** [January 19, 2021, 8:53pm UTC](https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867/3 "2021-01-19T20:53:27Z")

</div>

![Capture](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/e/f/efea5fbeaea8c1a4d8f6dcbd9d67f5e973036ad1.png)

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [January 20, 2021, 5:25pm UTC](https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867/4 "2021-01-20T17:25:13Z")

</div>

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.

Thanks,  
Will

---

<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:** [February 20, 2021, 3:25am UTC](https://devforum.zoom.us/t/bug-empty-recording-files-array-returned-in-users-me-recordings/40867/5 "2021-02-20T03:25:14Z")

</div>

Closed on February 20, 2021, 3:25am UTC

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