Trying to make sense of why the BYOC trunk configuration endpoint times out when I push concurrent JMeter threads. The environment details are below:
The API returns a 504 Gateway Timeout after 30 seconds. Standard calls work fine. Is there a specific rate limit for BYOC trunk updates that differs from standard routing queues?
Have you tried staggering the requests? The BYOC endpoint likely lacks the burst capacity of standard routing queues. Check the rate limiting headers in the response. Official API Docs suggest a 10-request-per-second cap. Aligning your load test with this limit prevents the 504 timeout.
Check your request payload size before hitting the endpoint.
Is there a specific rate limit for BYOC trunk updates that differs from standard routing queues?
The 10rps cap is correct, but large JSON bodies exacerbate the timeout. Reduce concurrency to 5 and add a 200ms delay between requests.
Have you tried adding Retry-After logic to your Java SDK client?
Is there a specific rate limit for BYOC trunk updates that differs from standard routing queues?
Yes. The 10rps cap is hard. 50 concurrent threads will always hit 504. Stagger the requests or implement exponential backoff in the code.