WFM schedule API drops 422 on Sydney edge during ACMA shift compliance import

Weekly roster update pushed through Terraform to mypurecloud.com.au. The /api/v2/wfm/schedules endpoint keeps rejecting the payload with a 422. ACMA mandates six-year shift retention tags on every block. It’s choking on the Melbourne timezone offset. Running the sync from LA timezone causes the clash. Latency spikes to 1.2s on the Sydney edge during validation. Console logs show the offset gets mangled. Retry loop isn’t helping. Doing jack all. Just spits out the same 422.