We’re hitting a wall with our outbound data actions in Architect. The goal is simple: fetch user preferences from our Kotlin backend before the IVR plays a personalized greeting. The endpoint is lightweight, just a simple GET request that returns a small JSON payload. Locally, the response time is under 200ms. In Architect, it’s failing consistently.
The data action is configured to call https://api.our-bpo.com/v1/user/prefs. The timeout is set to 3 seconds in the UI. We’ve tried lowering the concurrent request limit, adding retries, everything. The error log shows HTTP 504 Gateway Timeout. The backend logs show the request completing in 4.8s. It’s only a second over the limit, but Architect seems to hard-kill the connection exactly at 3000ms.
Here’s the payload structure we’re sending:
{
"userId": "${contact.id}",
"sessionId": "${session.id}"
}
And the response:
{
"language": "en",
"prefersVoice": true
}
We checked the Genesys Cloud API docs for POST /api/v2/architect/flows. There’s no field for timeout in the data action schema. The UI only allows setting it via the drag-and-drop interface, and the slider maxes out at 3 seconds. Is this a hard limit? We’ve seen other posts mention 10s or 30s timeouts for custom integrations, but those are usually webhooks or platform apps, not Architect data actions.
We’re considering moving this logic to a pure Kotlin microservice that handles the IVR flow via the REST API instead of using Architect. That feels like overkill for a simple preference check. Is there a hidden configuration or a support ticket required to bump the timeout? We’ve already tried clearing the cache and redeploying the flow. Same result. The 3s limit is too tight for our backend’s occasional latency spikes. We need at least 5s. Any ideas on how to force a higher timeout value in the JSON definition of the flow?