Outbound Campaign Pacing Timeout

General Discussion
1

Outbound Campaign Pacing Timeout

The POST /api/v2/outbound/campaigns endpoint is returning 502 errors during the America/Sao_Paulo peak window, and it’s completely ignoring the retry headers we’ve attached to Python SDK 2.11.4. New Relic traces show the transaction hanging at 9.1 seconds before the platform drops the connection, so is the pacing mutation endpoint rate-limiting silently?

{
 "code": 502,
 "status": "Bad Gateway",
 "message": "Upstream timeout on campaign pacing mutation"
}

Custom events are flooding the NRQL dashboard while the dialer queue stalls.