How does the analytics query builder handle offset pagination when pushing node traversal metrics and drop-off rates?
PureCloudPlatformClientV2 constructs the request body with strict validation on the flow version constraints. We are building a Java service to pull execution data for bottleneck detection. The initial payload looks like this: {"flowId": "a1b2c3", "version": 4, "metrics": ["nodeTraversal", "errorDistribution", "dropOffRate"], "timeRange": {"start": "2023-10-01T00:00:00Z", "end": "2023-10-08T23:59:59Z"}}.
The first call returns a 200 OK. When we append &offset=100&limit=100 for the next batch, the API throws a 400 Bad Request. The error says Invalid query parameter combination for historical trend analysis. We’ve tried wrapping the offset in the JSON body instead of the URL. Failed. We also verified the time range limits against the flow version constraints. Version 4 supports up to 30 days, so the window is valid.
Environment specs:
- Java 17, Spring Boot 3.1
- PureCloudPlatformClientV2 12.5.0
- CXone Flow Analytics API v2
- Offset-based pagination enabled
The bottleneck detection algorithm relies on consecutive data pulls to calculate latency across high-latency nodes and error-prone transitions. Right now the pagination breaks the sync to our CI/CD dashboard for developer feedback. We need the offset to carry forward without resetting the query context. How do we structure the pagination request so the doesn’t strip the offset parameter? Tracking analytics retrieval latency and data accuracy for monitoring is impossible when the flow analyzer drops half the dataset. The audit log generator is stuck waiting on the full dataset.