Data Action HTTP 503 on BYOC Trunk Metadata Enrichment in AP-Southeast-1

My configuration keeps failing when invoking the Data Action to enrich conversation_uuid with carrier-specific SIP headers from our 15 BYOC trunks in AP-Southeast-1. The flow v14.2.1 triggers an HTTP 503 Service Unavailable error during peak hours.

Error: 503 Service Temporarily Unavailable - Backend connection timeout

Failover logic appears intact, yet metadata enrichment fails consistently. Any insights on timeout thresholds for this integration?