Just noticed that bulk export jobs for digital interactions routed via Predictive Routing are omitting queue_id metadata. This breaks the chain of custody for legal discovery requests.
"metadata": {
"routing": null,
"queue_id": null
}
The recordings exist, but the routing context is stripped. Is this a known limitation with the Recording API for PR queues?