Why does this setting trigger a rate limit error when I scale the load test beyond 50 concurrent users? I am running a load test for an outbound dialing campaign using JMeter 5.6.2. The goal is to simulate high-volume dialing patterns. When the thread count stays below 50, the API calls to /api/v2/outbound/campaigns succeed without issue. However, once I increase the concurrent threads to 60, the response shifts to HTTP 429 Too Many Requests. The error message in the response body states: "message": "Rate limit exceeded for resource /outbound/campaigns".
I have verified that the OAuth token scopes are correct, including outbound:campaign:write. The issue seems isolated to the creation or update of the campaign status, not the actual call placement. I am using the Genesys Cloud API v2. My current JMeter configuration uses a constant throughput timer set to 100 requests per minute. Is there a specific configuration in the Architect flow or the campaign settings that lowers the threshold for API rate limits during bulk operations? I need to understand if this is a hard limit for the tenant or a misconfiguration in the request payload.