Quick question about screen recording metadata during bulk export for legal discovery. We are using Genesys Cloud with BYOC Edge and running bulk export jobs via the Recording API to S3. The issue is that the screen recording files (PNG/JPG snapshots) are missing the correct agent ID and interaction ID in the metadata JSON, even though the audio recordings have them. This is causing problems with chain of custody and audit trails for our legal hold requests. The API endpoint used is /api/v2/recordings/bulkexportjobs and we are seeing this consistently across multiple export jobs. The environment is running the latest patch version. I have checked the S3 integration settings and the IAM roles seem correct. The metadata JSON file generated by the bulk export job contains the interaction ID but maps it to the wrong agent in some cases. This is critical for our compliance requirements. Has anyone faced similar issues with screen recording metadata in bulk exports? Any insights on how to troubleshoot this would be appreciated. We need to ensure that every screen snapshot is correctly attributed to the agent and interaction for legal purposes.