I am running into a wall with an Architect Data Action that calls an external REST endpoint to fetch customer order history. The external service is pretty fast on its own, usually responding in about 1.5 seconds. However, when I wrap it in the Data Action, the whole flow times out. The error log in Architect shows a timeout exception after exactly 3 seconds. I checked the documentation and it seems like the default timeout for these actions is quite low. I need to bump this up to at least 5 or 6 seconds to give the external system enough breathing room.
Here is the JSON configuration I am using for the Data Action. It looks correct to me, but the timeout parameter doesn’t seem to be sticking or maybe I am putting it in the wrong place. I tried adding a timeout field in the root object, but that just caused a validation error.
{
"name": "GetCustomerOrders",
"type": "rest",
"url": "https://api.external-orders.com/v1/orders/{{user.id}}",
"method": "GET",
"headers": {
"Authorization": "Bearer {{oauth_token}}",
"Content-Type": "application/json"
},
"timeout": 5000
}
When I deploy this, Architect gives me a warning that the timeout is invalid. If I remove the timeout field, it defaults to 3000ms and fails. I have verified that the external endpoint is reachable and returns valid JSON within 1.2s if I hit it directly from Postman. The issue is strictly within the Data Action execution context.
I tried increasing the timeout in the Architect flow settings, but that only affects the overall interaction, not the specific Data Action step. I am wondering if there is a different syntax for setting the timeout in the Data Action JSON or if I need to use a different type of action, like a script action, to handle longer waits. I have spent the last hour tweaking the JSON structure without any luck. The documentation is vague about the exact schema for the timeout property. I need to know the correct way to extend this limit so the Data Action doesn’t kill the request prematurely.