Can anyone clarify the following regarding Predictive Routing exports for legal discovery:
- Bulk export jobs via /api/v2/recordings/export omit the routing_algorithm_id in metadata
- S3 integration receives files without the required hash for chain of custody verification
- Genesys Cloud v24.2 environment in Europe/London timezone
- Need to map specific predictive queues to agent skill profiles in the audit trail
- Current JSON payload lacks the routing_decision_timestamp field