Quick question about the Analytics Reporting API behavior when querying bot interactions routed through specific BYOC trunks. We are managing a complex multi-region setup with 15 BYOC trunks across APAC, and while the standard conversation metrics populate correctly, the sentiment analysis fields often return null or incomplete data for calls originating from our Singapore-based carrier. The endpoint GET /api/v2/analytics/conversations/details/query returns a 200 status, but the payload lacks the expected sentiment_breakdown object for approximately 15% of the records. This issue seems isolated to calls processed by the G.729 codec negotiation path, as G.711 routes appear unaffected. We have verified that the Architect flow is correctly configured to pass the interaction metadata and that the carrier is not stripping any headers that might impact the AI processing pipeline. The environment is running the latest stable release, and the OAuth scopes include analytics:read. Given the latency differences in APAC, could there be a known propagation delay or a specific configuration requirement for enabling sentiment scoring on low-bandwidth trunk connections? Has anyone encountered missing sentiment data specifically correlated with G.729 codec usage in BYOC environments, and is there a workaround to force the API to return these metrics?