Looking for some advice on troubleshooting this discrepancy in our recording metadata exports. We are using Genesys Cloud version 2024-3 in the eu-west-2 region. The issue is that WebRTC softphone recordings are not including the participant_identity field in the JSON manifest files generated by the bulk export job. This field is critical for our chain of custody documentation in legal discovery requests. The standard bulk export job completes with a 200 OK status, but when we inspect the resulting files in our S3 bucket, the participant_identity key is either null or missing entirely for WebRTC sessions. Voice trunk recordings via SIP are exporting correctly with full metadata. We have verified that the recording API v2 endpoints return the correct data when queried individually for specific recording IDs. This suggests the issue lies within the bulk export job processing or the Data Action configuration. We are using the default recording export settings with no custom transformations. Has anyone encountered this specific metadata loss for WebRTC channels? We need to ensure compliance with GDPR and internal legal hold policies. Any insights into whether this is a known limitation or a configuration error on our end would be appreciated. We are currently on hold with a major client pending resolution of this data integrity issue.