Architect Data Action timeout hard limit?

Architect & Flows
1

Does anyone know if there is a way to increase the default 3-second timeout for outbound data actions in Architect?

I have a simple HTTP POST to an internal endpoint that is consistently taking 4-5 seconds to process. I’ve optimized the payload size and the server response time, but Architect is killing the request with a generic timeout error before it completes.

Here is the flow:

  1. Data Action configured with POST method.
  2. Payload includes just a few key-value pairs.
  3. Target endpoint responds with 200 OK within 4.2s (verified via logs).
  4. Architect marks the action as failed.

I cannot find a property in the Data Action JSON config to override this limit. Is this a hard-coded platform constraint?

{
 "id": "action-123",
 "type": "outbound",
 "url": "https://internal-api.example.com/process",
 "method": "POST",
 "timeout": 3000 
}

If I set timeout to 5000 in the JSON, it seems to be ignored. The error message is just “Data action timed out.”

I need to handle these longer-running tasks without breaking the IVR flow. Any workaround or API flag I’m missing?

1 Like
2

You need to accept the 3s limit because architect won’t let you change it. offload the work to a queue like rabbitmq or sqs and have a worker process it asynchronously instead of blocking the call flow.

1 Like