Pushing outbound WhatsApp messages through the digital platform and hitting a wall. The flow uses the standard Send Message block, targeting a +61 formatted queue. Payload looks clean, but the endpoint keeps rejecting it with a 422 Unprocessable Entity. Error body points to message.invalid_destination_format. Checked the number formatting against ACMA guidelines and the sandbox test group. Everything matches.
Latency isn’t the issue. The request just drops immediately. Tried stripping the leading zero, added the country code explicitly, even swapped to the E.164 validator node before the send block. Nothing changes the response. Console logs show the flow executes fine until the HTTP POST to the messaging endpoint.
Running on the AU-1 region cluster. Custom wrapper’s on SDK version 2.14.3. You’d think the validator catches it, but it can’t parse the APAC locale override. The exact same payload works on US numbers without a hitch. ACMA compliance flags might be interfering with the template cache? Or maybe the routing profile needs a regional toggle for APAC hubs.
Raw response payload:
{
"message": "Destination number +61412345678 does not match approved template locale",
"code": "INVALID_LOCALE_MAPPING",
"status": 422
}