Speech to Text API Integration Fallback: Whisper Unavailable in Node.js Gaming Support

说明与用途

对于游戏支持队列，实际回退方案是具备稳定结果形状的提供商适配器：在每次批次前检查准备情况，尝试原生转录操作，当服务返回503或报告模型不可用时路由到Deepgram或AssemblyAI。

问题

For a gaming support queue, the native Whisper transcription route exists but its ASR models are marked unavailable, so transcription cannot be treated as a permanent dependency. The practical fallback is a provider adapter that checks readiness before each batch, tries the native transcription operation, and routes to Deepgram or AssemblyAI when the service returns 503 or reports model unavailability.

结果

The integration treats availability as data rather than a promise inferred from the existence of a route. A provider adapter checks model status before each batch, attempts native transcription, and routes to Deepgram or AssemblyAI on 503 or model-unavailable signals. The same consented player recordings can be replayed through different providers while downstream ticket decisions stay constant.

工作流

• Check ASR model availability via the model-status endpoint before each batch; log the availability result
• Attempt native transcription through /v1/audio/transcriptions
• If the native transcription fails with 503 or an error containing 'model not available', fall back to Deepgram or AssemblyAI
• Return a stable TranscriptResult record containing recording_id, text, provider, model_available, and error_class
• Keep the ticket classifier, evaluator, and human-review queue unaware of which speech provider produced the text

证据

For a gaming support queue, the practical fallback is a provider adapter with one stable result shape: check readiness before each batch, try the native transcription operation, and route to Deepgram or AssemblyAI when the service returns 503 or reports that the model is unavailable.

来源

The important constraint is current readiness. The model catalog marks ASR models available=false, so /v1/audio/transcriptions has the expected shape but is not currently a dependable service path.

来源

I initially expected the fallback to be a second try block around an SDK call. The sharper failure is earlier: a route can exist while its ASR model is unavailable.

来源

A failed transcription is retryable or visible to a human queue; a completed transcript can continue even when the selected provider changes on the next batch.

来源