Stuck on a critical compliance gap in our automated legal discovery workflow for digital channels. We are triggering bulk export jobs via the Genesys Cloud Recording API for WhatsApp conversations tagged with legal_hold status. The API returns a standard 200 OK, and the job completes successfully, but the resulting JSON manifests uploaded to our S3 bucket lack the necessary legal_hold metadata fields. This breaks our chain of custody audit trail, as the exported payloads do not reflect the hold status applied during the interaction. We are using the latest stable version of the Recording API and have verified that the source conversations in the UI correctly display the legal hold tag. The S3 integration credentials are valid, and other non-held recordings export without issue. Is there a known limitation with digital channel metadata propagation in bulk exports, or are we missing a specific query parameter in the export job definition? We need to ensure all exported artifacts maintain strict regulatory compliance for ongoing litigation. Any insights on how to force the inclusion of these specific metadata tags in the S3 payload would be appreciated. We have checked the audit logs, but they do not provide details on why the metadata was stripped during the export process.
I think the Recording API does not propagate custom metadata to the S3 manifest by default. 1. Map the legal_hold attribute in the Data Action. 2. Ensure the webhook payload includes the metadata key. 3. Verify the S3 bucket policy allows the specific tag.