Data Action HTTP Request Timing Out at 3s Despite Config Settings

Architect & Flows
1

Configuration is broken for some reason…

I am migrating a complex Five9 IVR script to Genesys Cloud Architect. The original Five9 script made a synchronous call to our internal order management system. In Five9, we could set the timeout to 10 seconds without issue. In Genesys Cloud, I am using a Data Action with an HTTP Request node to replicate this behavior.

The problem is that the request consistently fails with a timeout error after exactly 3 seconds. Our internal API sometimes takes 4-5 seconds to respond during peak load. I need to increase this timeout limit, but I cannot find where to configure it in the Data Action JSON or the Architect interface.

Here is the relevant section of my Data Action JSON:

{
 "name": "GetOrderStatus",
 "description": "Fetches order status from OMS",
 "parameters": {
 "orderId": {
 "type": "string",
 "defaultValue": ""
 }
 },
 "steps": [
 {
 "id": "httpRequest",
 "type": "httpRequest",
 "config": {
 "url": "https://oms.internal.com/api/v1/orders/{{orderId}}",
 "method": "GET",
 "headers": {
 "Authorization": "Bearer {{token}}",
 "Content-Type": "application/json"
 },
 "timeout": 10000
 }
 }
 ]
}

I have set timeout to 10000 milliseconds in the config object, but the execution log shows:

[ERROR] HttpRequestStep failed: Operation timed out after 3000ms

I have also tried setting the timeout in the Architect Data Action configuration panel, but it seems to default back to 3000ms on save. Is there a global setting for Data Action HTTP timeouts? Or is the 3-second limit hard-coded for security reasons?

If it is hard-coded, what is the recommended pattern for handling slow backend APIs in Architect? Should I move this to an external service and use webhooks?

Thanks for the help.

2

docs state “the default timeout for data actions is 3 seconds.” you need to override this in the node properties. set timeout to 10000 ms.

{
 "timeout": 10000
}

if it still fails, check your firewall. docs say “requests must complete within the configured timeout.”

3

The documentation actually says… you need to set timeout in the node properties.

TimeoutError: Request timed out after 3000ms

I usually bypass this by triggering a background job via /api/v2/integrations/webhooks, letting the external service notify Genesys when done. Synchronous Data Actions are too rigid for 5s latencies.

4

Have you tried setting the timeout in the HTTP Request node’s advanced properties? The 3s default is hard-coded unless explicitly overridden in the JSON config.

{
 "timeout": 10000
}
5

The way I solve this is by checking the node configuration JSON directly. The UI sometimes hides the timeout field or resets it. Ensure the timeout property is explicitly set in milliseconds, not seconds. If it still fails, verify your firewall isn’t dropping long-lived connections.

  • Node configuration JSON
  • Firewall rules
  • Millisecond vs seconds