Pushing evaluation criteria through the WFM interface and the Quality API keeps rejecting the payload. Targeting mypurecloud.com.au with the /api/v2/quality/evaluations endpoint. The request structure matches the docs, but the response throws a 400 Bad Request.
{"error_code": "invalid_request", "message": "Evaluation date format mismatch for region APAC"}
Console shows the evaluation is created locally, but the score sync for Sydney inbound traffic is doing jack all. Environment runs SDK v2.1.0. The flow includes an ACMA compliance recording block. Call ends, evaluation triggers, API fails.
Logs point to a timestamp issue. Header sends UTC, but the Sydney edge seems to expect a different offset. Queue targets +61 mobile numbers specifically. Changing the queue ID doesn’t fix the validation error. Hardcoding the date in the payload still results in the same rejection.
The evaluation criteria references a custom field for Australian number porting compliance. That field is populated correctly in the call data. API just won’t accept the date string when the call origin is Sydney.
2023-10-27T14:30:00+11:00
The error persists regardless of the timezone header.