Having some config trouble here 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 502 Bad Gateway error when querying the Analytics API v2 for trunk_id mapping. SIP registration is stable, and failover logic is intact. Is this a known limitation with outbound routing metadata enrichment under high concurrency in this region?