getting 429 too many requests when polling /api/v2/wfm/analytics/agents/realtime for a high-tenant count deployment. the app is a certified appfoundry premium app handling data sync for over 50 distinct organization ids. we are using the official genesys cloud rest api via node.js, not the architect sdk. the error payload is standard: {“errors”: [{“code”: “rateLimitExceeded”, “message”: “you have exceeded the rate limit for this endpoint”}]. we are strictly adhering to the documented limits of 10 requests per second per tenant. however, the aggregation service fires concurrent calls across multiple orgs to build a unified dashboard view. the timing seems to be the issue. if we stagger the requests by 100ms per tenant, the throughput drops significantly, causing data staleness in the ui. is there a batch endpoint for wfm analytics that we are missing? or is the rate limit calculated globally across the app’s oauth client id rather than per organization context? we have tried implementing exponential backoff, but the latency becomes unacceptable for real-time monitoring use cases. the environment is production, us-east-1. the app uses multi-org oauth scopes including wfm:agent:read and wfm:analytics:read. we have verified that the token is valid and has the correct permissions. the issue persists even after rotating the client secret. we are looking for a pattern to handle high-volume polling without hitting the ceiling. any insights on how other partners handle this at scale? we need to maintain sub-second refresh rates for critical kpis. currently, we are seeing timeouts on the client side after 3 retries. the api gateway logs show the requests are being rejected before they hit the backend service. this suggests the throttling is happening at the edge. we are open to using webhooks if they support wfm analytics events, but we have not found any documentation for that. please advise on best practices for multi-tenant polling strategies.