Pushed the updated Architect flow through Terraform v1.43.0 to mypurecloud.com.au last night. Flow version 22 deploys clean in the console, but runtime is breaking exactly when the call hits the ACMA recording validation step. The Make REST Call block tries to hit our internal compliance checker for +61 number porting status, then the trace just stalls. Sydney edge latency is sitting around 380ms right now. Doesn’t usually cause problems, but the flow execution engine seems to drop the payload completely.
Console shows a 408 timeout on the REST block, but the actual backend server logs confirm the request never arrived. Checked the flow trace. The data transform block before it serializes the ACMA timestamp as 2024-05-12T14:00:00+10:00. The Australian telecom regulator requires strict ISO 8601 with the AEST suffix, not the UTC offset. Wondering if the Genesys data mapper is stripping the timezone identifier during the JSON payload build. If you look at the platform logs, you’ll just see the generic timeout message.
Swapped the block to a simple DTMF capture just to test the media path. Audio routes fine, DTMF registers, but the moment the flow tries to evaluate the ACMA compliance flag, the contact drops. Provider logs show the flow execution hitting the evaluate node, then straight to disconnect with a flow_execution_error. No clear stack trace in the platform logs, just the generic timeout message.
Terraform state is locked to the Sydney region. Tried forcing the flow to run on the Melbourne edge via the routing profile, but it’s jumping to 600ms and the timeout happens faster. ACMA break window sync is running fine on WFM, so the issue is isolated to the Architect runtime environment. Flow trace attached below shows the exact node where it falls apart.
{
"nodeId": "rest_call_acma_check",
"status": "timeout",
"error": "flow_execution_error",
"timestamp": "2024-05-12T14:05:22+10:00",
"payload": {
"number": "+61298765432",
"acma_flag": true,
"timestamp_format": "invalid_offset"
}
}
Running Genesys Cloud v24.3.0 in the APAC region. The flow works perfectly on the US East sandbox, which makes this annoying. Just need to know if the Architect engine has a hard limit on timezone string parsing for Australian formats. The JSON payload builder keeps rewriting the offset.