422 Error on /analytics/recordings/detail Audio Filter in Tokyo Region

The GET /api/v2/analytics/recordings/detail endpoint returns a 422 Unprocessable Entity when filtering media type to audio in the Tokyo production environment. Console drops the audio duration metric entirely after the v2.8.4 SDK update. We’ve adjusted the request to bypass the filter and pull raw PCM streams via the export jobs, but the processing lag is doing jack all for the downstream fingerprinting pipeline and blocks any future speaker verification rollouts.

1 Like