Can’t get this config to load properly… Hitting 429 Too Many Requests on POST /api/v2/predictiverouting/outboundcampaigns when ramping to 20 concurrent threads in JMeter 5.6.2 from Singapore. The single-thread test passes without issue. I am trying to validate the API throughput limits for creating outbound campaigns during peak load scenarios. The error response body returns {“status”: 429, “code”: “TOO_MANY_REQUESTS”, “message”: “Rate limit exceeded”}. This happens almost immediately after the ramp-up starts, even though I am only hitting 20 requests per second. I have checked the Genesys Cloud documentation and it mentions rate limits are generally 100 requests per second for this endpoint, but maybe there is a stricter limit for campaign creation specifically? I am using the standard OAuth 2.0 client credentials flow for authentication. The JMeter script includes a constant throughput timer set to 20 transactions per second. I have also added a delay of 500ms between requests but the 429s still occur. Is there a specific header I need to include to handle pagination or rate limit retries? Or is this a known issue with the Predictive Routing API under load? I need to understand the exact capacity limits so I can plan our load testing strategy correctly. Any insights into the rate limiting behavior for outbound campaign APIs would be appreciated. I am also seeing some intermittent 503 errors mixed in with the 429s, which makes it harder to isolate the issue. The environment is the Genesys Cloud US-East region. I am running the tests from a Singapore-based EC2 instance to simulate international latency. The response times for the successful requests are around 200ms, which seems normal. But as soon as the concurrency hits 15 threads, the errors start appearing. I have tried reducing the concurrency to 10 threads and it works fine, but that does not help with our scalability requirements. We need to be able to create multiple campaigns simultaneously during our automated deployment process. Please let me know if there are any best practices for handling rate limits in JMeter or if I am missing something obvious in my configuration. Thanks in advance for any help.