Stuck on a problem and need help troubleshooting a Data Action timeout issue affecting our ap-southeast-1 BYOC trunks.
We are experiencing intermittent 504 Gateway Timeout errors when executing custom Data Actions designed to sync call metadata. The integration functioned correctly until the recent platform update. The failure occurs specifically during the metadata extraction phase for calls routed through our Singapore-based carrier connections.
Environment details: Genesys Cloud version 2023-11, Architect flow version 4.2. The Data Action utilizes the REST API to fetch SIP headers and carrier-specific routing data. Error logs indicate the timeout happens after 30 seconds, which aligns with the default Data Action execution limit.
SIP REGISTER status remains stable across all 15 trunks. Carrier failover logic appears intact, as calls successfully route during manual failover tests. The issue seems isolated to the data synchronization process rather than media transmission.
Has anyone encountered similar latency issues with Data Actions processing large volumes of BYOC trunk metadata? Looking for potential workarounds or configuration adjustments to extend the execution window or optimize the API calls.