Quick question about the Genesys Cloud Analytics API paging mechanism when exporting call detail records to Snowflake. I am using the Python SDK to fetch /api/v2/analytics/details/query, setting pageSize to 1000 to minimize HTTP overhead. The initial response returns 1000 records, a totalResults count of 45000, and a pageCount of 45. However, my loop condition relies on checking if the current pageNumber is less than the returned pageCount. On the second iteration, I increment pageNumber to 2 and make the request. The response returns another 1000 records, but the pageCount in the response body drops to 1. This causes my loop to terminate immediately after fetching only 2000 records, leaving 43000 records unprocessed. I have verified that the OAuth token is valid and has the analytics:details:view scope. I have also tried explicitly setting the pageNumber parameter in the request body versus query parameters, but the behavior remains identical. The documentation states that pageCount represents the total number of pages available, which should remain constant for a given query unless the underlying data changes, which is not the case here as this is a historical export. I need to understand if this is a known SDK quirk or if I am misinterpreting the paging object structure. Here is the relevant snippet of my request body: {“dateFrom”: “2023-10-01T00:00:00.000Z”, “dateTo”: “2023-10-02T00:00:00.000Z”, “pageSize”: 1000, “pageNumber”: 2}. The response header X-Genesys-Page-Count also reflects 1 on subsequent calls. This breaks my bulk extraction pipeline completely. How should I correctly handle pagination when the server-side pageCount field behaves dynamically? I suspect I might need to rely on totalResults and pageSize to calculate the expected page count myself rather than trusting the response object, but I want to confirm before refactoring the core extraction logic. Any insights on whether this is intended behavior or a bug in the v2 analytics endpoint would be appreciated. I have spent the last day debugging this and ruling out network timeouts and rate limiting issues. The data is static, so the page count should not fluctuate. Is there a specific header or query parameter I am missing that locks the pagination context?