Running into a wall with a Data Action in Architect. We’ve got a simple HTTP POST to an external vendor API that handles address validation. In local testing with curl, the endpoint averages 1.2s, but under load it spikes to 4-6s.
Architect’s Data Action config caps the timeout at 3000ms. There’s no slider or input field to go higher. When the vendor takes 4.5s, Genesys cuts the connection and returns a 504 Gateway Timeout to the IVR flow.
Is this a hard platform limit? We’re trying to avoid polling or async callbacks because the user experience suffers if we have to ask them to hold.
Here’s the JSON config we’re using for the action:
{
"type": "http",
"method": "POST",
"url": "https://vendor.example.com/v1/validate",
"headers": {
"Content-Type": "application/json",
"Authorization": "Bearer {{secure.token}}"
},
"body": "{ \"address\": \"{{input.address}}\" }"
}
The error response from the platform side looks like this:
{
"error_code": "timeout",
"message": "Data action execution exceeded maximum allowed duration"
}
We’ve tried adding a custom header X-Genesys-Timeout: 10000 but it gets stripped. Can’t find anything in the /api/v2/architect docs about global timeout overrides for specific actions either.
Anyone found a workaround for slow sync HTTP calls in Architect? We’re stuck with the 3s cap.