Dealing with a very strange bug here with the Architect flow when trying to append custom metadata headers to S3 export jobs for digital channel transcripts under legal hold. The environment is Genesys Cloud 2024-02. The flow triggers a bulk export via the API action, but the resulting objects in the S3 bucket lack the required x-amz-meta-legal-hold-id header. The standard PUT request to the bulk export endpoint succeeds with a 201 Created, yet the metadata mapping step in the Architect flow seems to ignore the JSON payload containing the custom headers. I have verified that the S3 integration policy allows s3:PutObjectTagging and s3:PutObjectAcl. The error does not appear in the flow logs, suggesting the issue lies in how the bulk export job processes the metadata injection. The chain of custody requirement is strict, so missing headers invalidate the evidence. How can I force the Architect bulk export action to include custom metadata headers for S3 objects?