How come this setting causes 429 errors on /v2/analytics/interactions? We are building a multi-org Premium App that aggregates interaction data across several Genesys Cloud instances. The integration uses OAuth 2.0 for authentication and queries the /v2/analytics/interactions endpoint with specific date ranges and query filters. Despite implementing exponential backoff and respecting the documented rate limits, we are still encountering 429 Too Many Requests errors during peak hours. The errors occur even when the request frequency is well below the stated limit per organization. We have verified that the OAuth tokens are valid and that the scopes include analytics:reports:read. The environment is a production deployment with approximately 50 concurrent users accessing the Premium App. We suspect there might be an aggregation issue or a hidden rate limit that applies across all organizations for a single app registration. Has anyone encountered similar behavior when querying analytics data for multiple organizations? We need to understand if there is a global rate limit that applies to the entire app or if there is a specific configuration that needs to be adjusted. Any insights into how Genesys Cloud handles rate limiting for multi-org Premium Apps would be greatly appreciated. We are currently investigating the possibility of implementing a more sophisticated queuing mechanism to handle these requests, but we want to ensure that we are not missing a fundamental configuration detail. The goal is to provide a seamless experience for our customers without hitting rate limits during critical reporting periods. We have also checked the API documentation for any notes on burst limits or throttling policies that might apply to Premium Apps, but the information is somewhat limited. We are looking for best practices or known workarounds that other partners have implemented when dealing with high-volume analytics queries in a multi-org environment.