Looking for advice on handling aggressive rate limiting when syncing evaluation forms via the Quality Management Platform API. Our AppFoundry integration manages quality standards across multiple Genesys Cloud organizations, and we have recently encountered persistent 429 Too Many Requests errors during bulk form updates. The issue arises when our service attempts to push standardized evaluation criteria to over fifty tenant instances simultaneously. We are using the endpoint PUT /api/v2/quality/evaluations/{evaluationId} to update form definitions. The error response includes a Retry-After header, but the suggested delay fluctuates significantly, ranging from 1500 to 4500 milliseconds. This variability makes it difficult to implement a stable retry mechanism within our synchronization job. We have already implemented exponential backoff logic in our Node.js SDK client, but the errors persist at scale. The current implementation respects the documented limits of 10 requests per second per organization. However, when aggregating requests across multiple tenants, the aggregate throughput seems to trigger platform-level throttling that is not clearly documented in the standard API guidelines. We are operating in a multi-org Premium App environment with OAuth 2.0 authentication. The integration uses service accounts with the Quality Admin role assigned at the organization level. We have verified that the authentication tokens are valid and have the necessary scopes. The problem appears to be isolated to the Quality Management API endpoints, as other API calls such as User Management and Routing Configuration complete successfully under the same load. We need to understand if there is a global rate limit for Quality Management API calls across all organizations within a single AppFoundry application. Additionally, we would appreciate guidance on best practices for batching these requests to avoid triggering the rate limiter. Our current approach involves parallel processing with a concurrency limit of five requests per organization. We are considering switching to a sequential processing model, but this would significantly impact the synchronization time for our clients. Any insights into the specific rate limiting thresholds for Quality Management APIs would be highly appreciated. We are currently using Genesys Cloud API version 2.0 and our integration is hosted in the US East region. The issue occurs consistently during business hours when network traffic is higher. We have attached the relevant error logs and request headers for further analysis. We are eager to resolve this to ensure reliable quality standard deployment across our client base.