From 42b002eea8a0bf5a727d8a87c77c98ab562c0abe Mon Sep 17 00:00:00 2001 From: Daniel Onyejesi Date: Wed, 25 Mar 2026 18:24:37 -0400 Subject: [PATCH] Add detailed error logging for Transcribe Medical failures Log error name, AWS metadata, and root cause to diagnose the "non-retryable streaming request" error. --- src/utils/transcribeAWS.js | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/utils/transcribeAWS.js b/src/utils/transcribeAWS.js index 0ee2b15..2bf5ee6 100644 --- a/src/utils/transcribeAWS.js +++ b/src/utils/transcribeAWS.js @@ -133,7 +133,11 @@ async function transcribeWithAWS(audioBuffer, mimeType) { transcript = await collectTranscript(medResp.TranscriptResultStream); console.log('[Transcribe] Medical transcription OK (' + transcript.length + ' chars)'); } catch (medErr) { - console.warn('[Transcribe] Medical failed, falling back to standard:', medErr.message); + console.warn('[Transcribe] Medical failed:', medErr.message); + if (medErr.name) console.warn('[Transcribe] Error name:', medErr.name); + if (medErr.$metadata) console.warn('[Transcribe] Metadata:', JSON.stringify(medErr.$metadata)); + if (medErr.cause) console.warn('[Transcribe] Cause:', medErr.cause.message || medErr.cause); + console.warn('[Transcribe] Falling back to standard Transcribe...'); // Fallback to standard Transcribe var client2 = new TranscribeStreamingClient({ region: region, credentials: credentials }); var StartStreamTranscriptionCommand = TranscribeModule.StartStreamTranscriptionCommand;