The scripting block keeps timing out on Sydney edge during morning routing. Terraform apply ran last night with provider v1.34.2. Flow version 14 deploys clean. Queue starts hitting +61 prefixes, then ACMA validation script stalls. Execution logs throw a 500 Internal Server Error on the ACMA_Compliance_Scrub block.
Console output points to regex compilation timeout. It’s supposed to just strip the leading zero and append country code for six-year retention tags. Runs clean in Virginia cluster. Pointing tenant at mypurecloud.com.au makes latency spike to 410ms. Scripting engine won’t hold thread past 2 seconds.
Checked flow JSON directly. Timeout parameter set to 5000 already. Still fails. Network traces from edge node show packets arriving fine. Response from flow execution service just hangs.
{
"blockId": "acma-scrub-v3",
"type": "Scripting",
"script": "var cid = data.callerId; return cid.replace(/^0/, '+61');",
"timeout": 5000
}
Error payload in console just returns SCRIPT_TIMEOUT_EXCEEDED. ACMA audit team is asking why compliance flags are missing from nightly export. Sydney edge routing table looks normal. Tenant memory sits at 11%. Don’t see any memory pressure. Can’t replicate it in staging.
Logs show thread vanishes exactly at 2150ms. Regex engine might be choking on local number formatting rules. Thread drops hard. No stack trace. Just the timeout flag.