Session.recording_transcript_failed Event – No Failure Reason or Retry Option

API and Webhooks
1

Hello Team,

We’re receiving the session.recording_transcript_failed webhook for some video sessions, but the payload doesn’t include any reason or diagnostic details. Could you please clarify:

  1. What causes this event to trigger?

  2. Is there a way to retry or requeue transcription for the same recording?

  3. Are there any logs or API endpoints that provide detailed error reasons?

Sample session ID: 642zvMi2QKStXRofEvfVYw==
Timestamp: 2025-10-22T09:49:19Z
Timezone: America/Chicago

We’d appreciate guidance or workarounds to handle failed transcription cases programmatically.

Thank you.

Sample webhook event :
{

 event: 'session.recording_transcript_failed',

payload: {

account_id: ‘SVS9zuAQSnO6DZBiCiXDnw’,

object: {

session_name: ‘68c2cef26214cd36a04991f7_1761125969934’,

start_time: ‘2025-10-22T09:49:19Z’,

timezone: ‘America/Chicago’,

session_id: ‘642zvMi2QKStXRofEvfVYw==’

   }

 },

event_ts: 1761126672209

}

Note : I received session.recording_completed event also for the same problematic session.

2

How long are the recordings where you’re seeing this failure? One possibility is that they are too short or don’t include enough spoken content, which could be causing transcription to error out and fail.

Zoom does not provide a direct API endpoint to manually retry or re-queue transcription for an existing cloud recording. The process is fully automated and tied to the initial recording upload, so once failed, it’s not reattempted natively.

As far as I know, there is not a method to get additional detail about the failure via the API, so we would need the Zoom team to look at their internal logs to get the full reason for the failures you’re seeing.

Is there any pattern you’re seeing in which sessions are failing to transcribe, or it seemingly random?

3

Hi @Amanda,

Thank you for the clarification. As of now we didn’t observe any pattern in failed calls and they appear intermittent. Since we don’t have access to detailed failure reasons via the API, could your internal team please review the logs for the sample session below to help identify the cause?

Sample session ID: 642zvMi2QKStXRofEvfVYw==
Timestamp: 2025-10-22T09:49:19Z

Additionally, please let us know if there are any recommended best practices or recording settings that might help avoid such transcription failures in the future.

Thanks again for your help,
Anjaneyulu.