Looking for advice on a discrepancy in our legal discovery exports. We have a complex Architect flow routing WhatsApp interactions. When the flow uses a specific ‘Save Conversation’ action, the subsequent bulk export to S3 misses the session_id link in the metadata JSON.
Error: Metadata validation failed. Missing required field ‘session_id’ for legal hold compliance.
Is this a known limitation with the Data Action API for digital channels, or should we adjust the flow logic?