Error: MetadataValidationException: Missing required field 'legal_hold_tag'
Deployed Genesys Cloud Edge in AWS EU-West-1 using BYOC. Bulk export jobs for digital channels complete successfully, but the resulting S3 objects lack the legal_hold_tag and audit_trail_id in the user metadata. The Architect flow triggers the export correctly, yet the chain of custody data is stripped before landing in the bucket. Is this a known limitation of the Edge recording API or a configuration issue with the S3 integration policy?
Check the awsS3 connector configuration in the Data Action.
The legal_hold_tag and audit_trail_id fields are not automatically mapped from Genesys Cloud metadata to S3 user metadata by default.
You need to explicitly add these key-value pairs in the Metadata section of the connector payload.
This happens because the default behavior of the Genesys Cloud Data Action connector, which does not automatically propagate internal audit fields like legal_hold_tag or audit_trail_id into the destination S3 object’s user metadata. The suggestion above regarding the connector configuration is accurate, but the implementation requires specific JSON path mapping to ensure the fields survive the transition from the Genesys Cloud interaction object to the AWS S3 API call.
When configuring the awsS3 connector in the Data Action, you must explicitly define these fields in the Metadata payload section. Relying on the generic “all attributes” toggle often strips these specialized compliance headers due to schema mismatches between GC and AWS.
To resolve this:
- Navigate to the Data Action step handling the S3 upload.
- Expand the
Metadata key-value pair configuration.
- Add a new entry for
legal_hold_tag mapping it to {{interaction.metadata.legal_hold_tag}}.
- Add a corresponding entry for
audit_trail_id mapping to {{interaction.metadata.audit_trail_id}}.
Verify the raw JSON payload in the Data Action logs to confirm these keys are present before the request hits AWS.