Hey folks,
Running into a wall with a Data Action in Architect. The external API I’m calling is slow-takes about 5 seconds to respond. The action keeps timing out and failing with a generic error. I checked the config and the timeout is set to 3000ms.
Is there a way to bump this limit via the API or is it just a platform hard cap? My JSON looks fine, just needs more time.
"timeout": 3000
You’re hitting a platform hard limit on the timeout property for standard Data Actions in Architect. It caps at 3000ms, and you can’t override that via the API or SDK. It’s just how the engine works right now.
If you’re managing this via Terraform, you’ll see the same restriction in the genesyscloud_flow resource. The timeout attribute for data actions is strictly bounded.
Your best bet is to move that slow call out of the synchronous path. Use a Data Action to kick off an async process, or better yet, use a Webhook action if you don’t need the immediate response in the flow state. If you absolutely need the data, consider using a genesyscloud_flow_action_data resource to wrap a faster endpoint that polls your slow service, but honestly, it’s a hack.
Here’s what the Terraform config looks like for the standard action, noting the timeout cap:
resource "genesyscloud_flow_action_data" "my_action" {
name = "Slow API Call"
flow_id = genesyscloud_flow.my_flow.id
method = "POST"
url = "https://example.com/slow-endpoint"
timeout = 3000 # Max allowed
headers = { "Authorization" = "Bearer {{token}}" }
}
Anything over 3000 gets silently clamped or rejected depending on the UI version. You’ll need to refactor the architecture if 5s is the norm.