Anyone free to help troubleshoot this spike in 429 Too Many Requests errors when pulling real-time analytics data via the Genesys Cloud API. We are running a JMeter script to validate how the reporting stack handles concurrent requests for call volume metrics.
The issue starts when we ramp up to 50 concurrent threads hitting GET /api/v2/analytics/conversations/details/summary. The response headers show retry-after values that fluctuate wildly, breaking our fixed-loop logic. We are using the standard OAuth2 client credentials flow and have verified the scope includes analytics:reports:read.
The environment is a standard Genesys Cloud instance in the Singapore region. We are not seeing any 5xx errors, just strict rate limiting. Is there a specific endpoint we should be using for high-throughput polling, or is this expected behavior for the summary endpoint under load?