Context:
Our enterprise contact center, operating primarily under the Europe/Paris timezone, has recently implemented a complex Architect flow involving multiple Data Actions to synchronize customer interaction history with our external CRM. The flow utilizes the standard Genesys Cloud Data Action connector for Salesforce. While the integration functions correctly during off-peak hours, we observe intermittent 504 Gateway Timeout errors when the queue activity exceeds 150 concurrent interactions. The specific error occurs at the ‘Update Case Record’ node, which is configured with a 30-second timeout. The logs indicate that the request is sent successfully, but the response from the external system is not received within the allocated window.
Question:
Can anyone clarify if there are known limitations on the number of concurrent Data Action executions per region or tenant? We have reviewed the performance dashboards and confirmed that our internal queue metrics remain within acceptable bounds. However, the latency appears to be introduced at the integration layer rather than the routing logic. Is there a recommended best practice for handling bulk data synchronization in high-volume scenarios without resorting to API-based custom integrations? We aim to maintain a purely declarative flow design for ease of maintenance and compliance auditing.