How come this setting causes a rapid increase in 429 responses when simulating concurrent agent script assignments?
We are validating the system capacity for agent script assignments during peak hours. The environment is Genesys Cloud US1, and we are using JMeter 5.6 to simulate 500 concurrent requests hitting the /api/v2/users/{userId}/scripts endpoint. The test fails after approximately 10 seconds with a high volume of 429 Too Many Requests errors. We have reviewed the API rate limits documentation, but it is unclear if there is a specific throttle for script assignment operations versus other user configuration updates. The goal is to determine if the current rate limit is sufficient for our expected load or if we need to adjust our JMeter configuration to spread the requests over a longer duration. Any guidance on the correct way to handle these rate limits during load testing would be appreciated. We want to ensure that our test results reflect realistic system behavior and not just artificial throttling due to our test setup.