Is it possible to increase the throughput for /api/v2/outbound/campaigns creation? Hitting timeouts consistently when pushing 50 concurrent requests via JMeter from Singapore. The campaign config is basic. Any hints on rate limits specific to outbound dialing?
campaign:
name: load_test_campaign
type: predictive
segment_id: seg_123
Getting 504s after 30 seconds.
This has the hallmarks of a classic case of hitting the platform’s default rate limiting thresholds for outbound campaign creation, especially when originating from a region like Singapore which might have higher latency to the primary US-based endpoints. The 504 Gateway Timeout indicates the request is being queued and then dropped before processing completes.
GET /api/v2/outbound/campaigns 504 Gateway Timeout
In ServiceNow integrations, we often see similar bottlenecks when firing multiple REST calls without proper backoff logic. The solution here is to implement exponential backoff with jitter in your JMeter script. Instead of 50 concurrent hits, stagger the requests. Also, verify if you are using the correct data center endpoint; sometimes routing through the wrong region adds unnecessary hops.
Try reducing the concurrency to 10 and adding a random delay of 500-2000ms between requests. If the issue persists, check the x-gc-request-id header in the response to trace the specific request in Genesys Cloud logs. This usually resolves the timeout issues by allowing the API gateway to process each campaign creation sequentially rather than overwhelming the queue.
Have you tried batching the campaign creation requests to respect the platform’s implicit rate limits?
{
"campaigns": [
{ "name": "batch_1", "type": "predictive" },
{ "name": "batch_2", "type": "predictive" }
]
}
Sending 50 concurrent POSTs to a single endpoint will always trigger the gateway timeout guardrails.