Just noticed that our JMeter scripts are hitting a hard wall when trying to push concurrent requests to the Agent Scripting API endpoints. We are validating the capacity of the platform to handle high-concurrency script updates during peak hours. The setup involves a dedicated BYOC edge in the ap-southeast-1 region. We are using JMeter 5.6.2 with a custom plugin to handle OAuth2 token refresh automatically. The target endpoint is /api/v2/scripts. We are sending POST requests to create new script versions. The ramp-up is set to 100 threads over 60 seconds. Each thread loops 10 times. The payload is a minimal JSON object with just the name and content fields. We are seeing a significant number of 429 Too Many Requests errors after the first 20 seconds of the test. The error response includes a Retry-After header with a value of 1 second. We have tried adding a constant timer of 1000ms between requests, but the 429 errors still occur. We have also tried reducing the concurrency to 50 threads, but the issue persists. The goal is to understand the rate limiting behavior for the Scripting API. We need to know the exact limits per tenant and per user. We are also interested in any best practices for handling rate limits in load testing scenarios. The current setup is causing our test results to be skewed. We are seeing a drop in throughput as the number of 429 errors increases. We have checked the API documentation, but it does not provide specific details on the rate limits for the Scripting API. We have also checked the Genesys Cloud status page, but there are no reported issues. We are using the latest version of the Genesys Cloud SDK for Java. The SDK version is 3.0.0. We have tried using the SDK to handle the retries, but it seems to be using a default retry policy that is not suitable for our load testing scenario. We have also tried using the JMeter HTTP Request Defaults to set the retry policy, but it does not seem to work. We are looking for a way to bypass the rate limits or to handle them more effectively in our JMeter scripts. We are also interested in any workarounds or best practices for testing the Scripting API at scale. How can we effectively handle the 429 rate limit errors when load testing the Genesys Cloud Agent Scripting API with JMeter, and what are the specific rate limits for this API?