- Has anyone figured out why the bulk export job fails with a 400 Bad Request when targeting predictive routing metadata for digital channels?
- Environment: Genesys Cloud BYOC EU-West-1
- Endpoint: POST /api/v2/bulkexports/exportjobs
- Filter: routing_prediction_id for digital interactions
- The API returns 400 Bad Request with ‘Invalid filter: routing_prediction_id is not supported for bulk export.’
- I need to export this data for legal discovery requests to maintain chain of custody.
- The recording_url filter works for voice and screen share interactions, but digital channels behave differently.
- My config is not working… The error payload is:
{
“code”: “invalid_filter”,
“message”: “Invalid filter: routing_prediction_id is not supported for bulk export.”,
“details”: “The filter field ‘routing_prediction_id’ is not available for bulk export jobs.”
} - I am using the Recording API to export metadata to our S3 bucket in EU-West-1 BYOC.
- The goal is to preserve audit trails for legal hold purposes.
- Any suggestions on how to achieve this without using the bulk export API?