Can’t quite understand why the /api/v2/predictiverouting/segments endpoint is throwing 429 Too Many Requests errors when running a JMeter script with 200 concurrent threads. The environment is set up in the us-east-1 region, and we are simulating a sudden spike in agent availability updates to test the routing engine’s capacity. The rate limit headers indicate x-genesys-remaining-rate-limit drops to zero almost instantly, even though the documentation suggests the default limit is higher for this tier. We are using the Genesys Cloud SDK v1.1.0 for Java, and the issue persists regardless of whether we implement exponential backoff. The goal is to validate that the predictive routing model can handle bulk segment updates without degrading performance for active calls. Any insights on how to tune the thread pool or adjust the API call frequency to stay within the limits while still achieving the desired load profile would be appreciated. We have tried spacing the requests by 50ms, but the throughput remains too low for our stress test requirements.