Need some troubleshooting help with a persistent 504 Gateway Timeout when invoking a custom Data Action designed to enrich SIP trunk registration logs. The flow hangs specifically at the HTTP Request block pointing to our internal carrier API, despite standard connectivity checks passing from the Genesys Cloud environment in the APAC region.
The Data Action is triggered via an outbound routing event on one of the 15 BYOC trunks. Logs show the request initiating correctly but never receiving a response payload before the default timeout threshold is breached. Increasing the timeout to 30 seconds did not resolve the issue, and no firewall blocks are detected on port 443. Looking for insights on whether this is a known limitation with external HTTP calls within Data Actions or a specific misconfiguration in the outbound proxy settings.