Architect Data Action 408 Timeout despite 3s config

I’ve got a Data Action set up to hit an internal REST endpoint. The timeout property is explicitly set to 3000 in the JSON definition. The endpoint itself is fast, usually returning in 200ms. However, the Architect trace is consistently showing a 408 Request Timeout error after exactly 3 seconds.

Here’s the relevant snippet from the Data Action config:

{
 "name": "FetchCustomerProfile",
 "type": "rest",
 "timeout": 3000,
 "url": "{{env.CUSTOMER_API}}/v1/profile/{{trigger.customerId}}",
 "method": "GET"
}

I assumed the timeout field was just a ceiling. Is there a hard global limit for Data Actions that overrides this setting? I tried bumping it to 5000 but the flow still fails at the 3-second mark.

Checked the server logs, the request never reaches the app. It’s being dropped by the platform before it leaves the Genesys edge. Any idea if this is a known cap or if I’m missing a config flag somewhere?