EnhancementQueueWorker silently falls back to STT credentials for LLM/diarization — confusing 401/404s #138

New issue

Closed

opened 2026-08-14 06:06:05 +00:00 by Mark · 0 comments

Mark commented

2026-08-14 06:06:05 +00:00

Owner

EnhancementQueueWorker's config building silently reuses generic cloud (STT) credentials when provider-specific fields are blank:

buildLLMConfig(): llmApiKey blank -> cloudSettings.apiKey (STT key) used as LLM key; llmEndpointUrl blank -> cloudSettings.endpointUrl (STT endpoint) used.
runDiarization(): diarizationApiKey blank -> cloudSettings.apiKey (STT key) used.

If a user configures STT (apiKey/endpointUrl) but leaves LLM or diarization fields blank, the worker sends STT credentials to the LLM/diarization provider, producing confusing 401/404 errors with no user-facing message explaining the mismatch.

Actual: mismatched provider credentials are sent silently; the failure surfaces as a generic 401/404 with no indication that the LLM/diarization settings are missing.
Expected: when provider-specific credentials are blank, either use the provider's own defaults explicitly, skip the feature with a clear user-facing message, or do not fall back to the STT key.

Reproduction: configure only STT apiKey/endpointUrl; run topic extraction with llmApiKey/llmEndpointUrl blank; observe the LLM request go out with the STT key.

Filed from kanban card t_a946c33c (post-deploy probe of Mark/transcriber#133).

EnhancementQueueWorker's config building silently reuses generic cloud (STT) credentials when provider-specific fields are blank: - buildLLMConfig(): llmApiKey blank -> cloudSettings.apiKey (STT key) used as LLM key; llmEndpointUrl blank -> cloudSettings.endpointUrl (STT endpoint) used. - runDiarization(): diarizationApiKey blank -> cloudSettings.apiKey (STT key) used. If a user configures STT (apiKey/endpointUrl) but leaves LLM or diarization fields blank, the worker sends STT credentials to the LLM/diarization provider, producing confusing 401/404 errors with no user-facing message explaining the mismatch. Actual: mismatched provider credentials are sent silently; the failure surfaces as a generic 401/404 with no indication that the LLM/diarization settings are missing. Expected: when provider-specific credentials are blank, either use the provider's own defaults explicitly, skip the feature with a clear user-facing message, or do not fall back to the STT key. Reproduction: configure only STT apiKey/endpointUrl; run topic extraction with llmApiKey/llmEndpointUrl blank; observe the LLM request go out with the STT key. Filed from kanban card t_a946c33c (post-deploy probe of Mark/transcriber#133).