{
"status": 422,
"code": "bad_request",
"message": "Invalid timezone offset for ACMA break window. Expected AEST/AEDT format."
}
Pushed the intraday roster config through Terraform v1.43.1 to mypurecloud.com.au last night. The /api/v2/wfm/intraday/adjustments endpoint keeps rejecting the payload when the shift crosses the ACMA mandated twenty minute break threshold. Sydney edge latency sitting around 390ms again. Console shows the state file applies clean, but the actual API call bombs on the startTime field.
Australian compliance requires the ISO 8601 duration string with the local offset baked in. Tried stripping the Z suffix and forcing +10:00, still hits the same validation error. It’s throwing the exact same block despite the org region being set to Pacific/Auckland. Queue managers getting flagged for non-compliant adherence reports. Roster sync falls behind by three hours every morning.
Checked the developer docs, nothing mentions the ACMA specific break formatting for the intraday endpoint. Terraform provider logs show a successful 200 on the initial POST, then a 422 on the follow up PUT for the break window. Network trace shows the Sydney edge node timing out the validation handshake.
Anyone else hitting this with the Australian number routing templates? The payload structure looks identical to what worked on the Melbourne edge last quarter. Swapped the provider to v1.42.8, same result. State file keeps marking the resource as tainted.
$ curl -X PUT "https://mypurecloud.com.au/api/v2/wfm/intraday/adjustments/adj_88392" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"adjustmentType":"break","startTime":"2024-05-14T06:30:00+10:00","duration":"PT20M","reason":"ACMA_COMPLIANT"}'
Response comes back with the 422 block again. Validation layer seems completely blind to the Australian standard offset. Logs are showing jack all for the actual handshake step. Edge node just drops the packet after the initial auth check.