Does anyone know why our bulk recording export jobs are failing with a 400 Bad Request error when targeting specific digital channel interactions? We are using the POST /api/v2/recordings/jobs endpoint to pull data for a legal discovery request. The job configuration includes filters for webchat and SMS sessions from the last 30 days. Voice recordings export without issue, but as soon as the filter includes digital channels, the job status moves to FAILED immediately. The error response body indicates ‘Invalid filter criteria for media_type’.
We have verified that the media_type values in our filter match the standard enumeration (webchat, sms). The S3 integration credentials are valid, as confirmed by successful test exports of voice data. This is critical for our chain of custody requirements, and we cannot proceed with the legal hold process until these digital records are secured. The environment is Genesys Cloud EU-1. We are using the Python SDK version 1.12.0 for the API calls. Any insight into whether digital channel metadata requires a different export mechanism or if there is a known limitation with the bulk job endpoint for these media types would be appreciated.