Azure: route azure_mini engine to gpt-4o-mini explicitly

The .env default DBN_AZURE_OPENAI_CHAT_DEPLOYMENT is gpt-4o, so the
azure_mini branch (which just called ->chat() without withDeployment)
was silently hitting gpt-4o too. Both UI engine options resolved to
the same model, and timed out together on long Norwegian documents.

Fix: explicitly route azure_mini → gpt-4o-mini in both timeline and
redact paths.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-05-15 09:38:55 +02:00
parent 85c3cee719
commit 55e11cb649
+4 -4
View File
@@ -367,8 +367,8 @@ PROMPT;
$response = $this->azure->withDeployment('gpt-4o')->chat($messages, $chatOptions);
$deployLabel = 'gpt-4o';
} else {
$response = $this->azure->chat($messages, $chatOptions);
$deployLabel = $this->azure->chatDeployment();
$response = $this->azure->withDeployment('gpt-4o-mini')->chat($messages, $chatOptions);
$deployLabel = 'gpt-4o-mini';
}
} catch (Throwable $e) {
dbnToolsAbort('LLM request failed: ' . $e->getMessage(), 502, 'llm_error');
@@ -1050,8 +1050,8 @@ PROMPT;
$response = $this->azure->withDeployment('gpt-4o')->chat($messages, $chatOptions);
$deployLabel = 'gpt-4o';
} else {
$response = $this->azure->chat($messages, $chatOptions);
$deployLabel = $this->azure->chatDeployment();
$response = $this->azure->withDeployment('gpt-4o-mini')->chat($messages, $chatOptions);
$deployLabel = 'gpt-4o-mini';
}
$content = (string)($response['choices'][0]['message']['content'] ?? '');