Why does this setting trigger rate limits when I scale up JMeter threads? I am running a basic load test against the Genesys Cloud platform API in the Singapore region. The goal is to validate concurrent screen recording sessions.
I have the screen_recording.enabled flag set to true in the arch flow. When I ramp up to just 30 concurrent users in JMeter, the API starts throwing 429 errors. This seems low for the documented limits.
Here is the error response body:
{
“code”: “rate_limit_exceeded”,
“message”: “Too many requests”,
“status”: 429
}
I am using the latest JMeter version with a simple HTTP request sampler. The endpoint is POST /api/v2/architect/flows. I am not using any complex scripting logic. Just a basic flow with a screen recording action.
Is there a specific header or parameter I need to include to avoid this? Or is the screen recording feature inherently more expensive on API calls? My JMeter config is pretty standard. I am using a loop controller with 10 iterations. The think time is set to 5 seconds. I am not sure if this is enough.
Any help would be great. I am new to this platform and trying to get the hang of the load patterns.