Does anyone know why legal hold tags are missing from our S3 exports? We trigger the Recording Bulk Export API (v2) for digital channels. The job returns 200 OK, yet the manifest.json lacks the legal_hold field. This breaks our chain of custody for discovery. We use the latest SDK. Is this a known bug with messaging archives?
You should probably look at at the export configuration settings, as legal hold metadata is often excluded by default in bulk exports to reduce payload size.
“manifest.json lacks the legal_hold field”
In Zendesk, we had to manually enable compliance tags for exports, and Genesys Cloud requires a similar toggle in the retention policy before the field appears.
My usual workaround is to:
- Verifying the retention policy explicitly includes compliance metadata.
- Checking if the export configuration filters out legal hold tags.
- Reviewing the manifest schema documentation for field availability.
it depends, but generally… check your jmeter payload. the default bulk export config often strips legal_hold to save bandwidth. you need to explicitly set include_legal_hold=true in the api call. just tried this in my load tests and it fixed the missing tags in s3.