Pushing a new evaluation template to mypurecloud.com.au and the Quality Management sync endpoint keeps rejecting the payload. It’s sitting at platform v2024.4.1. The template maps recording metadata fields for ACMA retention rules, but the /api/v2/quality/evaluationtemplates call throws a 422 Unprocessable Entity. Error response points straight to a mismatch in the recordingTimestamp format. Sydney edge expects ISO 8601 with a UTC+10 offset, while the WFM scheduler is injecting raw UTC strings pulled from the Berlin timezone. The validation layer won’t accept anything outside the expected APAC window. Stripped the timezone suffix locally as a quick workaround, which got the template to save, but the actual scorecard evaluation still fails when agents submit forms. The evaluationId comes back completely null in the JSON response. Latency between the EU management console and the Sydney media edge is dragging the sync request past the 12-second timeout window anyway. We’ve thrown in a retry header to bypass the initial drop, but that just masks the underlying schema validation error. Doing jack all to fix the root cause right now. The WFM capacity planning module is also flagging the same timestamp drift when pulling historical wrap-up codes. ACMA regulations require the exact +61 dialing prefix in the recording metadata, and the schema validator keeps stripping it out during the sync. Tried mapping the telephonyProvider field directly in the template JSON, but the API still chokes on the date string. The console just spins indefinitely when opening the evaluation dashboard. Mic stays hot on the test queue, but the scoring backend won’t process the submission. The payload structure looks perfectly fine in the sandbox environment.
{
“code”: 422,
“message”: “Timestamp format does not match expected APAC retention schema”,
“details”: [“recordingTimestamp must include +10:00 offset for ACMA compliance”]
}