Just noticed that our bulk export jobs for legal discovery are failing specifically for WebRTC sessions initiated via the latest softphone client update.
The issue appears when querying the /api/v2/recording/bulkexports endpoint. Jobs that previously completed successfully now return a 400 Bad Request error with the message “Invalid recording format for digital channel session”. This is happening exclusively for recordings tagged with softphone version 10.2.5 running on Windows 11. The metadata payload in the request body matches our standard template used for other digital channels like WhatsApp and Email.
We are operating in the eu-west-1 region. The recordings exist in the system and are playable via the UI, but the export job fails to queue. We have verified that the user scopes include recording:export:read and recording:export:write. The chain of custody logs show the job starts but immediately transitions to FAILED status. No other error details are provided in the response body. Has anyone encountered a compatibility issue between the new softphone codec and the bulk export service? We need to resolve this urgently as we are behind schedule on a major legal hold request. The standard export API also fails for these specific IDs, suggesting the issue is at the storage or encoding level rather than the job scheduler.