Running into a wall with a simple HTTP POST data action. The target API is solid, responds in about 400ms under normal load. But once latency creeps up past 3 seconds, the data action fails hard.
Here’s the JSON config I’m using:
{
"name": "PostToLegacy",
"type": "http",
"url": "https://api.internal/data",
"method": "POST",
"timeout": 5000
}
I’ve explicitly set timeout to 5000. Checked the docs. Nothing mentions a hard cap at 3000ms. Yet, in the Architect logs, I see:
DataActionExecutionException: Request timed out after 3000ms
It’s always exactly 3 seconds. Not 3.1, not 2.9. Just 3.0.
Tried changing it to 10000. Same error. Tried 2000. Works fine. It seems like the timeout property is being ignored or overridden by a system default of 3s.
Is there a hidden global setting for data action timeouts? Or is this a known limitation of the platform that requires a ticket to change? We’re not using the SDK here, just the native Architect data action builder.
Any ideas on how to bump this past the 3s mark? We can’t refactor the backend API to be faster right now.