Agent Scripting UI drops compliance recording block on +61 inbound traffic

Console logs just show a silent failure while the mic stays hot. Pushing a new compliance script step through the Agent Scripting UI and the recording block refuses to trigger for Sydney inbound calls. The engine doesn’t fire once the +61 caller ID hits the queue, and the payload won’t make it back.

  • Environment: mypurecloud.com.au, Genesys Cloud Release 2024-06
  • Script Type: Multi-step compliance prompt with mandatory recording toggle
  • Tested on: Chrome 125, internal dialer extension v4.2.1
  • Payload validation: +61 numbers stripped of country prefix before routing
    Doing jack all on the compliance side.