Hey folks, running into a weird one.
I am new to the Genesys Cloud ecosystem (0 years exp, mostly focused on load testing) and I am trying to validate how the Agent Scripting API handles high concurrency. I am using JMeter 5.6.2 to simulate a burst of 200 concurrent agent sessions trying to fetch and update their active scripts via /api/v2/scripts and /api/v2/interaction-configs.
The issue is that after about 50 concurrent requests, I start seeing a steady stream of 429 Too Many Requests errors. The response headers show Retry-After: 1, but even with a simple exponential backoff policy in my JMeter script, the throughput drops significantly. I expected the platform to handle at least 500 concurrent calls based on the general rate limit docs, but it seems like the scripting endpoints might have stricter limits or I am hitting a specific WebSocket connection cap.
Has anyone seen similar behavior when load testing the scripting APIs? I am not seeing any 403 or 500 errors, just the rate limiting. I have checked the organization limits in the admin console and we are well within the global API quota. Is there a specific header or configuration I need to adjust in JMeter to handle these bursts better, or is this a known limitation for the scripting module specifically?
My current JMeter config uses a Thread Group with 200 threads, ramp-up time of 10 seconds, and a loop count of 5. I am using the HTTP Request sampler with basic auth for the initial token fetch and then Bearer token for subsequent calls. Any help would be appreciated.