Agent script prompt block drops 400 on Sydney edge during ACMA consent injection

Pushed new agent script flow via Terraform v1.50.2 to mypurecloud.com.au around 0900 PST. Apply ran clean, but Sydney edge won’t accept prompt block during ACMA consent injection. Flow version 18 deploys updated regex for Australian mobile numbers, yet media server drops 400 Bad Request when script tries to play recording disclaimer. Console shows script asset as published, and prompt block references correct S3 bucket for AU region. Latency spikes to 320ms on inbound leg, which probably messes with SIP INVITE timing. Error log spits out {"code":"invalidPromptAsset","message":"Media timeout on edge gateway"} every time agent enters wrap-up. Swapping audio format from MP3 to WAV is doing jack all. Gateway still chokes on codec negotiation.

Ran the POST /api/v2/scripts endpoint directly from Postman to bypass state file, and response matches Terraform output exactly. Architect debugger shows prompt block timing out at 4500ms before DTMF capture triggers. Script configuration uses standard genesyscloud_script resource, but prompt object refuses to bind ACMA compliance string. Edge logs show repeated SIP/2.0 488 Not Acceptable Here codes pointing to media resource pool. Script asset ID matches console, yet playback engine throws 404 for localized voice file. ACMA rules require exact disclaimer wording, so we can’t just swap it. Flow continues, but agents get dead air instead of consent audio. Checking raw JSON payload for prompt block…