Hey everyone, I’ve run into a really strange issue with 429 Too Many Requests when testing outbound dialer capacity.
the environment is us1. i am using jmeter 5.6 to simulate high volume outbound calls. the goal is to push 500 concurrent dial attempts against the campaign api to see where the bottleneck is. i have configured the jmeter thread group with a ramp-up time of 10 seconds and a loop count of 10. each thread sends a post request to /api/v2/outbound/campaigns/{campaignId}/contacts to initiate the dial sequence.
the issue happens very quickly. after about 50 successful dial initiations, the api starts returning 429 errors. the response header shows retry-after: 2. this is strange because the documented rate limit for outbound apis is much higher than 50 requests per second. i have checked the architect flow and it is simple: answer → play greeting → transfer to agent. there are no complex rules or external http requests in the flow that could cause delays.
i also checked the websocket connection limits. the softphone clients are not connecting yet, so there should be plenty of capacity there. the problem seems isolated to the outbound campaign api endpoint.
is there a specific limit on how fast contacts can be queued for a single campaign? or is this a global api limit that i am hitting? i have tried adding a constant timer of 200ms between requests in jmeter, but the 429 errors still occur. this makes it hard to get an accurate measurement of the max throughput.
any help would be appreciated. i need to know if this is a configuration issue on my side or a hard limit in genesys cloud.