Data Action 502 on BYOC Trunk Metadata Enrichment

Hey everyone, I’ve run into a really strange issue with Data Actions trying to enrich conversation metrics with carrier-specific latency stats from our AP-Southeast-1 BYOC trunks. The REST call hits the internal analytics endpoint but returns a 502 Bad Gateway intermittently. This breaks the downstream reporting flow.

  • Validated the API key scopes include analytics:view and trunks:view.
  • Confirmed the target endpoint responds correctly via Postman outside the Architect flow.