No idea why this is happening, the script retrieval endpoint is throttling us so aggressively during the initial ramp-up of our JMeter test. We are trying to validate the load capacity for a new omnichannel deployment in the APAC region.
The flow is straightforward: Agent login → Fetch Script → Start Interaction. The script fetch uses GET /api/v2/scripts/{scriptId}. With just 50 concurrent threads hitting this endpoint within a 10-second window, we start seeing 429 responses. The headers indicate we are hitting the rate limit for the script resource group.
We assumed the script content would be cached after the first fetch per agent session, but it seems every thread is triggering a fresh API call. Is there a way to bypass this limit for read-only operations during load testing, or are we missing a caching configuration in the JMeter setup?
Here is the relevant JMeter HTTP Request configuration:
http_request:
path: "/api/v2/scripts/${scriptId}"
method: "GET"
headers:
Authorization: "Bearer ${access_token}"
concurrent_threads: 50
ramp_up_seconds: 10
The error response body is empty, just a 429 status. Any ideas on how to structure the test to respect these limits without slowing down the overall test execution?