The paging object in the Genesys Cloud Analytics API is behaving unexpectedly for my conversation queries. I’m using the JavaScript SDK to pull historical conversation data, specifically targeting the /api/v2/analytics/conversations/queues/summary endpoint. The documentation states that pageSize determines the number of results per page, and pageNumber indicates the current page index. However, when I set pageSize to 100 and request pageNumber 2, the response body returns a pageCount of 1, but the entities array contains 100 items. This contradicts the expected behavior where pageCount should reflect the total number of pages available based on the total result set size.
Here’s the relevant code snippet from my request:
const analyticsApi = new platformClient.AnalyticsApi();
const params = {
pageSize: 100,
pageNumber: 2,
query: 'interval=2023-01-01T00:00:00.000Z/2023-01-02T00:00:00.000Z&group_by=queueId'
};
analyticsApi.postAnalyticsConversationsQueuesSummary(params)
.then(response => {
console.log('Page Count:', response.pageCount);
console.log('Total Entities:', response.entities.length);
})
.catch(err => console.error(err));
The output shows pageCount: 1 and Total Entities: 100. I’ve verified that the total number of conversations for the queried interval is significantly higher than 100, so there should be multiple pages. Is there a known issue with how the SDK calculates or returns the pageCount? Or am I misinterpreting the query parameter structure? I’ve tried adjusting the interval and group_by parameters, but the issue persists. I need to paginate through all results to aggregate data, so this blocking issue is critical. Any insights on whether this is a bug in the SDK’s response parser or an API-side inconsistency? The raw HTTP response headers also don’t include X-Page-Count, which makes client-side pagination logic difficult to implement reliably. I’m stuck on whether to trust the pageCount field or implement a custom loop based on the presence of entities in the response.