Trying to understand why screen_recording_url is null in the /api/v2/analytics/conversations/details response for specific BYOC trunk sessions. Environment is Genesys Cloud 2023-12, BYOC Edge 10.5.0.2. The recording files exist in S3 and are accessible via direct URL, but the analytics payload lacks the reference. Terraform config for the recording policy is standard. resource “genesyscloud_quality_recording_policy” “main” { name = “Prod-Recording” enabled = true recording_type = “audio_and_screen” … } The GC CLI shows the policy is applied to the flow. Flow version 14. Screen recording is enabled in the Architect flow under the “Wrap-up” stage. When checking the conversation logs via CLI, the status is “completed” with no errors. However, the analytics export job returns empty values for the screen media object. Is there a specific delay for metadata propagation in BYOC environments? Or is the screen_recording_url field only populated after a post-processing step that might be failing silently? The audio_transcript_url is present, so the pipeline is partially working. Checking the S3 bucket permissions shows the Genesys service role has full read/write access. No 403 errors in the CloudWatch logs for the BYOC edge. The issue is consistent across three different agent IDs. Need to confirm if this is a known limitation with the current edge version or a configuration gap in the recording policy HCL. Any insights on forcing a metadata refresh or debugging the analytics pipeline for screen media?