Encountering a 400 Bad Request error when triggering the Create Recording Export Job data action within an Architect flow. The export is configured for legal discovery purposes, specifically targeting digital channel interactions. The payload includes standard metadata fields, but the request fails immediately when the interaction_id corresponds to a WhatsApp message rather than a voice call.
Environment details:
- Genesys Cloud EU (London)
- API Version: v2
- Export Destination: BYOC S3 Bucket
- Data Action: Create Recording Export Job
The error response body indicates invalid parameters related to the interaction type. Voice recordings export without issue. However, WhatsApp interactions, which are required for the current legal hold request, cause the job to abort. The chain of custody requirements mandate that all digital messages be included in the bulk export, not just voice files. The S3 bucket permissions are verified and working for other export types. It appears the system does not support exporting WhatsApp metadata alongside voice recording metadata in the same job configuration, or there is a specific field causing the schema validation to fail.
How can I successfully export WhatsApp interaction metadata for legal discovery without triggering a 400 error in the bulk export job?