Running the /api/v2/analytics/interactions/queries endpoint against our US org, but telephony is provisioned through mypurecloud.com.au. Pulling CDR data for compliance audits is doing jack all when date range crosses thirty days. The Python SDK v3.0.2 throws a 422 Unprocessable Entity with {"errors":["Query execution exceeded the maximum allowed time of 30000ms"]}. The architect flow is standard IVR to queue, recording enabled, ACMA seven-year retention toggled on in org settings. Latency between the Sydney edge and US analytics backend seems to be the culprit. Call durations are also off by roughly two hundred milliseconds in the dashboard. Breaks our SLA reporting completely.
Tweaking the intervalSize to PT1H won’t fix the underlying timeout. The query builder in the UI just spins forever. It’s probably choking on the aggregation service. Logs show the request hits the gateway but drops before the service processes the Australian number ranges. +61 2 prefixes seem to trigger the timeout consistently. The SDK retry logic just exhausts the rate limit. The aggregation service can’t handle the cross-region latency without a custom timeout override.
{
"maxRetries": 3,
"backoff": "exponential",
"queryTimeoutMs": 30000
}