Can’t get this config to load properly. We rely on a Data Action to push weekly schedule changes to an external HRIS. The integration works fine for small batches. It fails hard when we publish the full Chicago shift roster. The Architect flow hangs at the HTTP Request step. We get a 504 Gateway Timeout after exactly 30 seconds. This happens every Tuesday morning during the publish window. The external API logs show no request received. It seems the Genesys Cloud side drops the connection. We are using the standard HTTP Outbound integration. The payload size is under 500KB. Latency to the target endpoint is low. I suspect the Data Action execution context is timing out. Is there a way to increase the timeout for this specific action? Or should we split the batch into chunks? The current setup blocks our weekly workflow. We need a reliable sync mechanism. Any pointers on optimizing the Architect flow would be appreciated.
I’d suggest checking out at the HTTP request timeout settings. The default 30-second limit is too short for large roster payloads.
Increase the timeout to 60 seconds in the Data Action configuration. This prevents the gateway from dropping the connection before the external system can respond.