Context:
Running into a weird bug with a Data Action configured in our primary inbound flow (version 4.2.1). The action calls a legacy SOAP endpoint that occasionally hangs, resulting in a 504 Gateway Timeout within Genesys Cloud. This failure causes the interaction to bypass the final queue entry node, creating a significant discrepancy in the ‘Handled Interactions’ metric on the Performance dashboard versus the actual voice volume.
Question:
Is there a configuration setting in the Architect flow to define a stricter timeout for Data Actions, or must this be handled via the external service provider? We need to ensure the conversation detail view captures the failure reason for audit purposes.