Struggling to figure out why the Agent Scripting API returns rate limit errors when the concurrent thread count is well below the documented threshold for our tier.
Error: 429 Too Many Requests - Rate limit exceeded for endpoint /api/v2/agent-scripts
Environment details:
Genesys Cloud US1 region.
JMeter 5.6.2
Endpoint: /api/v2/agent-scripts
Config: 100 concurrent threads, ramp-up 10 seconds
The goal is to validate the throughput for bulk script updates before a major deployment. The test simulates 100 agents simultaneously updating their active script assignments. According to the API documentation, the rate limit for this endpoint should allow for higher concurrency, but the test fails consistently after approximately 20 successful requests.
The error response body indicates:
{
"errors": [
{
"code": "rate_limit_exceeded",
"message": "You have exceeded the allowed rate limit for this resource."
}
]
}
The OAuth token refresh mechanism is functioning correctly, as verified by a separate authentication test. The issue appears strictly related to the request volume hitting the Agent Scripting endpoint.
Questions:
- Is there a specific rate limit for /api/v2/agent-scripts that is lower than the general API limit?
- Should the JMeter config be adjusted to include a delay between requests to avoid triggering the rate limiter?
- Are there any known issues with the Agent Scripting API under high concurrent load in the US1 region?
Any insights or recommendations for handling this rate limit during load testing would be appreciated. The current setup causes the test to fail prematurely, preventing accurate assessment of the system’s capacity for bulk script updates.