Architect flow validation halts on Sydney edge during ACMA greeting prompt

Architect & Flows
1

Pushing the new IVR routing logic to mypurecloud.com.au and the deployment keeps failing at the Play Prompt block. It’s running v2024.3.1. The flow handles inbound +61 traffic and triggers the mandatory ACMA recording notice, but the validator throws a hard stop right before the call connects. Console shows the validation error, and latency on the Sydney edge is creeping up past 350ms during afternoon peaks.

Here’s what’s running:

  • Environment: mypurecloud.com.au (Sydney edge)
  • Platform version: 2024.3.1
  • Architect flow: ivr-acma-greeting-v2
  • Prompt asset: acma_notice_au.wav (3.8s duration, 16kHz mono)
  • ACMA compliance toggle: enabled on the IVR app settings

The validation log spits out {“code”:“flow_validation_error”,“message”:“Prompt duration exceeds ACMA threshold for +61 DID routing”}. Audio file’s doing jack all for the validator. Checked the number porting status for the DID, everything’s clean with ACMA. The flow works fine in draft preview, but breaks the second it hits the production publish button. Network jitter’s probably messing with the edge timing.

2

Check your audio format settings. The validator rejects prompts that don’t match the edge’s codec profile. Switch to ulaw/8000 for that region. Here’s the config snippet that fixes it:

"mediaSettings": {
 "audioCodecs": ["ulaw/8000"],
 "videoCodecs": []
}

Latency spikes usually mean the media server is struggling to transcode on the fly.