Screen Recording Metadata Missing in Bulk Export

How should I properly to ensure screen recording metadata is included in the bulk export payload? we are processing a legal discovery request and need the full chain of custody. the v2 bulk export job completes successfully but the resulting s3 files lack the interaction_id linkage for screen captures.

using filter type=screen_recording returns empty sets. the api returns 200 ok but the manifest file is incomplete. this breaks our audit trail requirements for the case.

If I remember right, the bulk export endpoint doesn’t handle screen recordings the same way as standard voice interactions. The type=screen_recording filter often returns empty sets because the backend treats these as separate media artifacts rather than primary interaction records.

using filter type=screen_recording returns empty sets. the api returns 200 ok but the manifest file is incomplete.

The issue is likely that you are querying the interaction list directly. Screen recordings are linked via the interactionId but are not always returned in the primary bulk export job unless explicitly requested as a media attachment. Try switching to the media export API instead.

POST /api/v2/recording/exports
{
 "filters": [
 {
 "field": "mediaType",
 "operator": "eq",
 "value": "screen"
 }
 ]
}

This forces the system to pull the specific media objects. The standard bulk export might be skipping them to save throughput. Check if the includeMedia flag is set to true in your initial job creation payload.

Check your data action configuration for the metadata sync step. The bulk export often fails to link screen recording artifacts because the underlying data action times out when querying the media store for high-volume interactions. This is a known latency issue in the APAC region, particularly when dealing with large batches.

The type=screen_recording filter is not supported directly in the bulk export API. Instead, you need to query interactions by interaction_id and then fetch the media artifacts separately. Ensure your data action handles pagination correctly to avoid the 504 gateway timeout I’ve seen in similar setups.

If you are still seeing empty sets, verify that the screen recording feature is enabled in the application settings. Without this, the media store will not retain the files, resulting in an incomplete manifest.