Why does this setting break chain of custody for WebRTC exports?

Background

Running bulk exports to S3 for legal discovery using Genesys Cloud Recording API v2.

Issue

Why does this setting cause the JSON manifests to omit conversation_id when the source is a WebRTC softphone? The audio files arrive in the bucket, but the metadata gap breaks our chain of custody requirements.

Troubleshooting

  • Verified standard voice recordings export correctly.
  • Checked S3 permissions; no errors logged.
  • Confirmed WebRTC interactions are marked as ‘recorded’ in the UI.