Agent Scripting REST API rejects ACMA opt-out payload with 400 validation error on AU edge

Pushed the compliance script to /api/v2/architect/scripts via the nightly pipeline. Sydney agents are stuck on the ACMA mandatory opt-out phrase requirement. Console throws a 400 Bad Request with invalid_script_structure. It’s looking clean in Postman but the APAC edge rejects it every time. Number formatting is doing jack all for us right now. Injecting the 02 prefix DIDs into the initial_prompt block triggers the validator immediately. Stripped the leading zero, swapped to E.164 +612, and the error shifts to missing_required_compliance_element. ACMA rules are strict about local formatting for inbound recordings. Latency to the US core is sitting around 180ms. Maybe causing a timeout on the schema check? Not sure. Architect v2.14.3 is running locally. SDK’s locked to genesyscloud@2.118.0. Can’t bypass the validation with ?skipValidation=true since the endpoint just ignores the flag. Queue config is live. Scripting block is failing deployment. Pipeline keeps failing on step 4. Reverted to hardcoded prompts. Dynamic routing logic is completely broken now. Flow architecture expects a dynamic variable but the validator hardcodes the region check.