Quick question about the metadata propagation during bulk exports for digital channels under legal hold.
Context:
We are running a Genesys Cloud instance (2024-Q1) and using the Analytics API to trigger bulk export jobs for WhatsApp and SMS transcripts tagged with legal_hold=true. The export targets our S3 bucket. While the JSON files arrive successfully, the custom metadata headers defined in the Architect flow are missing from the S3 object metadata. This breaks our chain of custody verification scripts.
The Architect flow uses the “Create Bulk Export” action with specific metadata key-value pairs. In previous voice exports, this worked fine. However, for digital channels, the S3 objects only contain standard AWS metadata. We checked the job status via GET /api/v2/analytics/bulkexports/{id} and it shows completed with no errors.
Question:
Is there a known limitation with digital channel exports regarding custom metadata injection into S3? Or is there a specific permission or configuration step required for the S3 integration to accept custom headers for non-voice media types? We need to ensure the legal discovery team can verify the integrity of these exports.