{
"code": "invalid_message_content",
"status": 400,
"message": "Template validation failed for locale en-AU. ACMA mandatory opt-out phrase not detected in first 160 bytes."
}
Pushed the digital queue config through the CI/CD pipeline yesterday. Everything is compiling fine in Architect until WhatsApp template validation step runs. Sydney edge latency is sitting at 145ms. Shouldn’t be an issue for a sync API call, but /api/v2/messaging/validate keeps timing out right before content check completes. Switched routing to US East edge for testing. Validation passes instantly. Issue definitely tied to APAC message routing cluster.
Using 2024.7.0 SDK wrapper for deployment script. Payload looks standard. Injecting the ACMA required phrase “Reply STOP to unsubscribe” at very start of template. Character count is 142. UTF-8 encoding. Compliance team says phrasing matches ACMA Code of Conduct exactly. API keeps rejecting with 400 error above.
Checked flow debug logs. Digital engagement node passes payload to messaging connector. Connector logs show request hitting APAC gateway, then dropping. Retry logic doesn’t trigger. Tried swapping to standard SMS channel instead of WhatsApp Business. Same validation failure. Locale flag in JSON set to en-AU. Regex pattern inside parser probably runs an old version. Added trailing period, still fails. Removed period, still fails.
Pipeline stuck on this step. Need digital channel live for Melbourne rollout next week. Template validation service might be running outdated pattern that doesn’t recognize standard ACMA wording. Looking at raw request headers in trace. Content-Type is application/json. Auth token refreshes correctly. Timeout only happens when APAC edge selected in routing policy. Telephony and digital routing are provisioned through mypurecloud.com.au domain. The payload structure matches schema exactly.