Screen Recording API 404 on BYOC Trunk Associated Flows

Does anyone understand why the GET /api/v2/conversations/{conversationId}/recordingmetadata endpoint returns a 404 for interactions routed through our AP-1 BYOC trunks? The flows are identical to PSTN routes, yet the recording metadata is missing from the analytics payload entirely. This discrepancy is breaking our carrier failover compliance reports.