Looking for advice on a recurring 422 Unprocessable Entity error when configuring bulk export jobs for digital channel recordings in our BYOC environment.
Context:
We are operating in a Bring Your Own Cloud setup with AWS S3 as the destination. The standard recording exports for voice channels are functioning correctly. However, when attempting to export WhatsApp interaction recordings with the include_metadata flag set to true, the job fails immediately during the configuration phase.
The error response indicates that the metadata schema requested is invalid for the specified export type. Specifically, the payload includes legal_hold_status and chain_of_custody_hash, which are required for our legal discovery workflow. The API documentation suggests these fields are supported for digital channels, yet the validation fails.
Question:
Is there a known limitation with metadata field inclusion for WhatsApp recordings in BYOC edge deployments? We are using the Recording API v2 endpoints. The same configuration works without issue in our standard Genesys Cloud instance, leading us to believe this might be an edge-specific validation rule or a mismatch in the metadata schema definition for digital media in isolated environments.