My configuration keeps failing correctly for our outbound campaign scripts. The flow fails after 12 seconds with a 504 Gateway Timeout error. This only happens on our Singapore-based BYOC trunks. The SIP registration status remains healthy throughout the session.
We are using Genesys Cloud version 2023-11-Q4. The issue persists across all 15 trunks in the region. Standard inbound calls work fine without any latency. Outbound scripting seems to trigger a different routing path.
The error logs show the timeout occurs at the initial media handshake. We have verified the carrier failover logic is intact. No packet loss is detected on our SBC logs during these failures.
Has anyone seen similar delays with agent scripting on APAC trunks? We need to adjust the timeout thresholds or identify the bottleneck. Any insights would be appreciated.
Ah, yeah, this is a known issue…
{
"dataAction": {
"name": "ScriptTimeoutAdjustment",
"type": "http",
"settings": {
"timeout": 30000,
"retryCount": 2
}
}
}
The 12-second default for HTTP data actions in Architect flows is often insufficient for APAC BYOC trunks due to increased latency. The Performance Dashboard usually shows these as successful completions in the queue view, but the flow logs will capture the 504 error.
Adjusting the timeout threshold in the data action settings to 30 seconds typically resolves this. Additionally, check the queue activity metrics during peak hours. If the platform is throttling requests, the wait_time metric may spike, causing secondary timeouts. Ensure the SIP registration remains stable, but the primary fix lies in the flow configuration rather than the trunk settings. This approach maintains compliance with legal hold requirements by ensuring the script completes before the recording metadata is finalized.