Why does the outbound campaign start endpoint hits 429 so quickly? Running JMeter 5.6.2 from Singapore. Targeting /api/v2/outbound/campaigns. Simulating 50 concurrent requests. Hitting 429 immediately. Need help understanding the rate limit structure for campaign operations.
The goal is to validate how many campaigns can be activated simultaneously during peak hours. The current setup uses HTTP Request defaults with basic auth. The request body includes standard campaign configuration.
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 1
{
“errors”: [
{
“code”: “429”,
“message”: “Rate limit exceeded”
}
]
}
The error appears after about 10 requests. The Retry-After header suggests waiting one second. However, the load test continues to fail. The JMeter thread group has a ramp-up period of 10 seconds. The loop count is set to 1. The sampler timeout is 30 seconds.
I have checked the API documentation. It mentions rate limits for outbound operations. However, the specific limits for campaign activation are not clear. The documentation suggests using exponential backoff. But the test fails before backoff can be applied.
The environment is Genesys Cloud standard edition. The organization has multiple campaigns. The test is run during off-peak hours. There are no other active load tests. The network latency to Singapore is low. The server response time is under 200ms before the 429 error.
I am looking for the exact rate limit for campaign activation. Also, any best practices for handling 429 errors in JMeter. The current script does not handle retries. Adding a retry controller might help. But I want to understand the limit first.
Any insights would be appreciated. The test needs to simulate realistic campaign activation patterns. The current failure rate is too high. This blocks the performance validation phase. Need to adjust the concurrency or request rate. But I need the numbers first.