Can anyone explain why the legal_hold metadata is being stripped from our bulk export jobs for WhatsApp transcripts? We are executing POST /api/v2/recordings/exports requests for a legal discovery case, but the resulting JSON files in S3 lack the required compliance flags. The Architect flow correctly applies the hold status, yet the export payload seems to ignore it.
The environment is running the latest Genesys Cloud release, and we are using the standard Recording API for this task. We have verified that the source recordings have the legal_hold attribute set to true in the UI. However, when the bulk export job completes, the metadata section in the output files is empty regarding this specific field.
This discrepancy is causing issues with our chain of custody documentation. We need every transcript to explicitly show the hold status for audit trails. The S3 integration itself is functioning correctly, as the files are uploaded without error codes like 400 or 500. The problem is strictly with the data integrity of the exported metadata.
We have checked the documentation for the Recording API but found no mention of this behavior for digital channels. Is there a known limitation with WhatsApp transcript exports, or is this a bug in the current version? Any insight on how to force the metadata retention would be appreciated.