Pushed the roster sync through Terraform v1.42.1 to mypurecloud.com.au last night. The /api/v2/wem/agents/adherence endpoint keeps rejecting the payload when the shift crosses the ACMA mandated twenty-minute break window. Console shows a 400 Bad Request with {"error":{"message":"Invalid adherence interval for region APAC-SYD"}}. Flow version 22 deploys fine locally but the WEM data action chokes on the +61 timezone offset. Latency from Melbourne to Sydney edge sits around 180ms, so it’s not a network timeout. The script attempts mapping the compliance break to standard wrap-up code and API doesn’t even parse the offset correctly. Adjusted the startTime and endTime to UTC, but the ACMA retention tag still triggers the same response. Adherence report generates partially then stops at the 14:00 mark. Logs show the interval boundary check failing on the second payload batch. Running curl directly against the endpoint returns the exact same 400. Payload structure matches the docs, just the region field seems off. The API is doing jack all with the daylight saving shift.
{"error":{"code":"VALIDATION_ERROR","message":"Interval crosses unsupported regional compliance boundary"}}