Pushed the weekly compliance dashboard sync through the nightly GitHub Actions run against mypurecloud.com.au. Latency on the outbound sync is fine, but the /api/v2/analytics/reporting/reports/execute endpoint just rejects the ACMA payload with a 422 when start_date uses AEST format. SDK version 1.14.2 handles the auth fine, yet the Sydney edge doesn’t take the daylight saving offset properly. Console dumps this exact response:
{
"message": "Invalid date format for AEST timezone",
"code": "invalid_date_range"
}