We are building a custom integration where a Genesys Cloud Data Action calls an internal microservice. The endpoint is simple, but it does a database lookup that takes about 4-5 seconds to return a result.
We configured the Data Action in Architect with a timeout of 3 seconds. The call fails every time with a timeout error. We tried increasing the timeout in the Architect UI, but it seems capped or the validation rejects higher values. We also checked the API documentation for PUT /api/v2/architect/flows and looked at the JSON structure for the data action node, but didn’t see a clear property to override the HTTP client timeout beyond the standard settings.
Here is the current configuration for the data action node:
{
"id": "dataaction-1",
"type": "dataAction",
"dataActionId": "12345",
"timeout": 3000
}
The error log in the flow execution trace shows:
Error: Request timed out after 3000ms. Status: 408
Is there a way to increase this limit programmatically or via the API? Or is there a workaround like using a different node type? We need the response to complete without dropping the call. The endpoint is definitely responding within 5s, we’ve verified that with Postman.