Context:
Managing a distributed environment with 15 Bring Your Own Carrier (BYOC) trunks across multiple regions, including a significant cluster in AP-Southeast-1. The current operational requirement involves automated SIP credential rotation to comply with carrier security mandates. This process is orchestrated via a custom Data Action triggered by an Architect flow. The specific endpoint in question is POST /api/v2/integrations/data-actions. The payload includes the necessary trunk identifiers and the new SIP credentials formatted according to the carrier specifications for Singapore and Malaysia regions.
The integration logic has been validated in staging environments without issue. However, when deployed to the production tenant, the Data Action consistently fails after approximately 30 seconds. The response body indicates a 504 Gateway Timeout. The timeout occurs specifically when the system attempts to sync the new credentials with the underlying BYOC trunk resources in the AP-Southeast-1 region. Other regions, such as US-East and EU-West, process the same Data Action payload successfully within the expected 5-second window. This discrepancy suggests a potential latency issue or a specific configuration bottleneck within the AP-Southeast-1 data center affecting the integration service’s ability to communicate with the trunk management backend.
Question:
Can anyone clarify if there are known limitations or specific configuration requirements for executing Data Actions that modify BYOC trunk credentials in the AP-Southeast-1 region? The 504 Gateway Timeout is blocking our automated security compliance workflows. We have verified that the SIP credentials are valid and that the carrier endpoints are reachable from our network. The issue appears isolated to the Genesys Cloud integration layer’s timeout threshold for this specific region. Is there a way to extend the timeout duration for these specific Data Actions, or is this indicative of a deeper infrastructure issue within the AP-Southeast-1 environment that requires escalation to support? Any insights into optimizing the payload or the execution context for regional trunks would be appreciated.