Trying to understand why a Data Action within a Genesys Cloud Architect flow consistently returns a 504 Gateway Timeout when querying internal metadata for Singapore BYOC trunk IDs. The flow executes correctly for US trunks but fails specifically when the trunkId parameter matches our APAC carriers.
HTTP/1.1 504 Gateway Timeout
Content-Type: application/json
{
"code": "GatewayTimeout",
"message": "Operation timed out"
}
The internal endpoint responds under 100ms in direct testing, so the delay appears to originate within the Genesys Cloud execution environment during peak APAC hours.