What is the reason this setting causes immediate failures when invoking custom data actions from Architect? The integration returns a 504 Gateway Timeout after exactly thirty seconds, halting the customer journey. We are operating in an EU-West BYOC environment. The business requirement is to validate customer eligibility against a legacy CRM system before routing to the appropriate skill group. The current flow includes a Data Action module configured with a timeout of thirty seconds. When the external system takes longer than this threshold, the flow fails with an HTTP 504 error. The error message displayed to the caller is a generic system failure prompt. This results in a significant drop in first call resolution rates. The Performance Dashboard shows a spike in abandoned calls during peak hours. The queue activity view indicates that these calls are not being counted as handled interactions. This discrepancy affects the agent performance metrics. The conversation detail views show the call duration as zero seconds. We need to understand if there is a way to extend the timeout beyond thirty seconds. Alternatively, we are looking for a best practice to handle these timeouts gracefully. The current configuration prevents the flow from proceeding to the next step. The business impact is substantial. Customer satisfaction scores are declining due to the abrupt disconnections. We have reviewed the Architect flow documentation. The documentation states that the timeout is configurable. However, we have not found a method to increase it beyond the default limit. The environment details are as follows. Genesys Cloud version is 2024.1. The integration uses a REST API endpoint. The response time from the legacy system varies between twenty and forty seconds. We need a reliable solution to prevent these timeouts. Any insights on configuring the Data Action module for longer response times would be appreciated. We are also interested in understanding how these failures impact the overall queue metrics. The current setup is not sustainable for our operations. We require a stable integration that can handle variable response times. Please advise on the recommended approach. We are open to alternative flow designs if necessary. The goal is to ensure seamless customer interactions. We want to avoid any abrupt disconnections. The current error handling is insufficient. We need a more robust mechanism to manage these scenarios. Your guidance on this matter is highly valued. We are eager to implement a solution that meets our business requirements. Thank you for your assistance.