So I’m seeing a very odd bug with the Analytics API when pulling queue performance data for our Paris operations. The environment is Genesys Cloud v2.8.5, and we are using the standard REST endpoints (/api/v2/analytics/queues/data). During the peak shift (09:00-11:00 CET), the dashboard integration begins to fail with HTTP 429 Too Many Requests errors, despite our request rate being well below the documented limit of 60 requests per minute. The specific error payload returns "error_code": "rate_limit_exceeded" and "message": "Request rate limit exceeded". We have verified the x-genesys-request-id headers, and the latency spikes correlate exactly with the start of the shift. Interestingly, this does not happen during off-peak hours or on weekends, even when the volume of concurrent sessions is lower. We are not using any custom scripts or third-party SDKs; this is a direct integration from our internal reporting tool using Python requests library v2.31.0. The issue persists across multiple user tokens, suggesting it is not tied to a specific user’s rate limit bucket but rather an account-wide or region-specific throttling mechanism. We have checked the Developer Portal documentation for any recent changes to the rate limiting strategy, but nothing indicates a change in the last quarter. The problem is causing significant delays in our real-time performance monitoring, which is critical for our WFM team in Paris. We need to understand if there is a hidden throttle for bulk analytics queries during high-load periods or if there is a configuration setting in the Admin Portal that we are missing. Is there a way to increase the rate limit for analytics endpoints, or should we be implementing a specific retry strategy with exponential backoff to mitigate this? Any insights into the current rate limiting behavior for the queues/data endpoint during peak hours would be greatly appreciated.