Does anyone understand why the Data Action step in our Architect flow is failing with a 500 Internal Server Error when attempting to map the carrierId attribute for calls routed through our AP-SE-2 BYOC trunks? The flow is designed to enrich conversation data before passing it to our external analytics platform. We have verified that the SIP registration is stable and the carrierId is correctly populated in the initial SIP INVITE headers. However, when the Data Action attempts to retrieve the specific trunk metadata using the /api/v2/telephony/providers/edges/trunks/{trunkId} endpoint, the response times out or returns a generic server error. This issue started appearing after the SDK v2.14.0 update. The error log shows: DataActionError: Failed to fetch resource: 500 Internal Server Error. We have checked the Genesys Docs and confirmed the field mapping syntax is correct. Is there a known latency issue with the analytics API in the AP-SE-2 region for BYOC trunk metadata retrieval? The failover logic is working, but the data enrichment step is breaking the flow for approximately 30% of inbound calls.