Data Action Timeout in Architect Flow

Looking for advice on a Data Action timeout issue in our primary routing flow. The HTTP POST to our internal CRM returns 200 OK, yet the flow logs a generic timeout error after 5 seconds, despite the payload being small. This occurs consistently during peak hours in the Paris region.

The dashboard shows increased queue abandonment correlating with these failures. Can you clarify if the timeout applies to the TCP handshake or the full response body? We need to determine if this is a network latency spike or an Architect configuration limit.