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.