# Different and strange results when query\_date\_type set to archive\_complete\_time

**URL:** <https://devforum.zoom.us/t/different-and-strange-results-when-query-date-type-set-to-archive-complete-time/80228>\
**Category:** Archiving\
**Tags:** api\
**Created:** [December 13, 2022, 4:27pm UTC](https://devforum.zoom.us/t/different-and-strange-results-when-query-date-type-set-to-archive-complete-time/80228 "2022-12-13T16:27:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.bennington](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david.bennington/32/26896_2.png) [@david.bennington](https://devforum.zoom.us/u/david.bennington)\
**Post date:** [December 13, 2022, 4:27pm UTC](https://devforum.zoom.us/t/different-and-strange-results-when-query-date-type-set-to-archive-complete-time/80228/1 "2022-12-13T16:27:04Z")

</div>

Endpoint: /v2/archive\_files

I cannot link the events directly, they belong to a customer of ours.

When querying for archive events with a date range, let’s assume a single ‘meeting’ is returned. This event contains 10 archive\_files, with per participant recordings enabled. Everything looks ok. However, adding the `query_date_type=archive_complete_time` to the request results in three separate ‘meeting’ entries in the json array, all with the same meeting id/uuid. Each of these meetings differs in start time and duration (yes, for the same uuid) , however all 3 contain the same 10 archive\_files (every field is identical).

I would expect the result to either be the same - a single archive event with 10 files, or 3 events with _different_ files. Not all being the same.

This customer has per-participant recordings enabled and has been doing some testing recently, which may have an involvement.

No errors are reported.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [December 15, 2022, 11:07pm UTC](https://devforum.zoom.us/t/different-and-strange-results-when-query-date-type-set-to-archive-complete-time/80228/2 "2022-12-15T23:07:23Z")

</div>

Hi @david.bennington ,

Thanks for sharing. A visual would be helpful. Can you please message me the JSON response and meeting info so I can see the behavior you’re describing? Thank you!

You may also provide account id and production client id in case a service engineering ticket is necessary for further review.

Best,  
Gianni

---

<div class="post-metadata">

**Author:** ![david.bennington](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/david.bennington/32/26896_2.png) [@david.bennington](https://devforum.zoom.us/u/david.bennington)\
**Post date:** [December 16, 2022, 3:07pm UTC](https://devforum.zoom.us/t/different-and-strange-results-when-query-date-type-set-to-archive-complete-time/80228/3 "2022-12-16T15:07:48Z")

</div>

Gianni,

I’m not comfortable in providing the exact json, as it’s not data that belongs to us, certainly not in a public forum. I could redact it and provide that to you if that helps demonstrate, please let me know. The meeting uuid in question is v64xXIw/QASdRhtQVlOb8A==, and our app id is fgAhEWF2TUyvNrcGV32RJQ.

I don’t know the zoom account id as we have authenticated with oauth and it’s not readily available to me.

David
