Pushing a new compliance validation step through the Platform API and the Sydney edge keeps rejecting the request. Targeting mypurecloud.com.au with the /api/v2/architect/flows/{flowId}/steps endpoint. The JSON mapper throws a 422 Unprocessable Entity right when the ACMA recording consent block tries to bind to a +61 mobile prefix. Console shows the latency spiking to 1.8s before the timeout, which is pretty weird for a basic POST. The request body doesn’t look malformed. It’s matched the schema exactly, but the response payload keeps flagging invalid_au_number_format even though the E.164 structure is correct. Running SDK v10.4.2 for the integration scripts. Tried stripping the leading zero, tried keeping it, same result. The Sydney edge routing rules seem to be applying an older ACMA validation filter that won’t accept the standard prefix. Payload just ghosts out doing jack all. Logs show a silent rejection on the compliance webhook.
{ “error_code”: “422”, “message”: “Validation failed for AU compliance step”, “details”: [ “Field: phone_number_prefix”, “Reason: ACMA format mismatch” ] }