Hi Zoom Developer Team,
We are experiencing an issue with the cursor-based pagination on the agent_timecard historical dataset API. The same next_page_token returns different data on repeated requests, causing data loss during pagination.
API Endpoint:
GET /v2/contact_center/analytics/dataset/historical/agent_timecard
Parameters:
- page_size: 100
- start_time_from: 2026-06-09T00:00:00Z
- start_time_to: 2026-06-10T00:00:00Z
- sort_order: asc
- next_page_token: jlnlwumJOYqPyKoMOOONeL77suSNm2nyMR5 (3rd page)
Issue:
When we send two identical requests with the exact same next_page_token and parameters, the API returns different records in different order. For example:
Request 1, first record: work_session_id = 1ff3cd7c-5fa2-4f39-a68c-5382eb401165 (Jordan Xiong)
Request 2, first record: work_session_id = d731eb2d-c732-4ff6-b48b-f8e51a5d1a40 (Kenny Jensen)
Both records have the same start_time (2026-06-09T14:37:43Z), and the total_records count is consistent (1658) across both requests. However, the ordering within the page is not stable.
Impact:
This unstable sort order causes records at page boundaries to be either skipped or duplicated during pagination. In our case, we consistently see 1-3 records missing per month when syncing the full dataset.
Expected Behavior:
The same next_page_token should always return the same set of records in the same order, regardless of how many times the request is made.
Environment:
- API Version: v2
- Region: US
- Zoom Contact Center licensed account
We have screenshots demonstrating the issue and can provide additional details if needed.
Thank you for looking into this.