Looking for advice on Architect flow failures during digital channel exports. The IVR node sets legal_hold: true in the session, but the subsequent S3 upload omits this tag. The Recording API returns the correct metadata when queried manually, yet the bulk export job strips it. Is there a specific configuration in the Architect integration to preserve custom metadata for discovery requests? The audit trail is incomplete without this flag.
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 session variables often drop if not mapped to a persistent Custom Attribute. Verify the S3 Export job configuration includes the specific custom attribute ID in its field mapping list.