Need some troubleshooting help with a data integrity issue with POST /api/v2/recordings/exports. We are pulling WhatsApp transcripts for a legal discovery request, but the resulting S3 files are missing the legal_hold flag in the JSON metadata. The Architect flow sets this correctly, and our IAM role has full S3 permissions. The export job completes with status completed, yet the metadata is stripped. Is this a known limitation for digital channels?
The way I solve this is by ensuring the legal_hold attribute is explicitly defined in the Architect flow’s Data section before the recording ends. The bulk export process relies on static schema definitions, so dynamic attributes are ignored. See KB-9921 for details.