We’ve got a Data Action calling an external endpoint that’s just sitting right at the edge of the timeout window. The integration takes about 4-5 seconds to process and return JSON, but Genesys Cloud is killing the request after exactly 3000ms.
I dug into the documentation for the genesyscloud:external:rest:fetch action, and I see the timeout parameter defined as an integer. I tried bumping it to 10000 in the JSON mapping, hoping to get a 10-second window. The platform accepted the configuration without validation errors, but the runtime behavior didn’t change. The call still fails with a 408 Request Timeout status code in the Data Action logs after precisely 3 seconds.
Here’s the relevant snippet from our Data Action configuration:
{
"id": "genesyscloud:external:rest:fetch",
"name": "FetchUserProfile",
"properties": {
"url": "https://api.internal-service.com/v1/profile",
"method": "GET",
"timeout": 10000,
"headers": {
"Authorization": "Bearer {{ token }}"
}
}
}
Is there a hard-coded global limit on Data Action execution time that overrides the property setting? I can’t find any mention of a maximum timeout value in the API reference. The only workaround I’m seeing is to move the logic to a Genesys Cloud Flow with a longer timer, but that adds unnecessary latency for a simple API call. If the 3-second limit is enforced at the infrastructure level, what’s the recommended pattern for handling external services that naturally take 5-7 seconds to respond?