Encountering consistent 429 Too Many Requests errors when invoking PUT /api/v2/wfm/scheduling/shifts for bulk shift updates across multiple tenant contexts. The application is a Premium AppFoundry integration handling high-volume workforce adjustments. While the initial OAuth2 token acquisition succeeds without issue, the subsequent batch operations trigger rate limiting almost immediately after the first 50 requests per tenant. The error payload indicates a retry-after header of 120 seconds, which is disruptive for real-time synchronization requirements. The integration uses the Genesys Cloud REST API directly via Node.js, adhering to the documented best practices for pagination and batching. Despite implementing exponential backoff, the throughput remains significantly below the expected capacity for a multi-org deployment. The issue appears isolated to the WFM module, as other platform APIs like Analytics and Conversations continue to operate within normal limits. This throttling behavior suggests a potential discrepancy between the documented rate limits for standard API keys and those applied to AppFoundry service accounts in a multi-tenant architecture. Is there a specific configuration or quota adjustment required for WFM endpoints in this context, or is this a known limitation of the current API gateway implementation for premium integrations?