From 4aeca36a9c3ed670ec92fe6b8ad48c5ea906989b Mon Sep 17 00:00:00 2001 From: Michelle Date: Tue, 14 Jul 2026 12:30:17 +0200 Subject: [PATCH] fix: log underlying network error cause for failed transcription requests Co-Authored-By: Claude Opus 4.8 --- server/config/transcription.js | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/server/config/transcription.js b/server/config/transcription.js index 27969fd..d9bf6c3 100644 --- a/server/config/transcription.js +++ b/server/config/transcription.js @@ -62,7 +62,10 @@ export async function requestTranscription({ meetingId, recordingId, prompt }) { log.server.info(`Transcription requested for recording ${recordingId} (meeting: ${meetingId})`); return true; } catch (err) { - log.server.error(`Transcription request error: ${err.message}`); + // undici wraps the real network error (ECONNREFUSED, ENOTFOUND, timeout, …) + // in err.cause — surface it, "fetch failed" alone is undiagnosable. + const cause = err.cause ? ` (${err.cause.code || ''} ${err.cause.message || ''})`.trimEnd() : ''; + log.server.error(`Transcription request to ${url} failed: ${err.message}${cause}`); return false; } }