Report #29286
[gotcha] Retry button with temperature=0 returns identical failed result, making the AI appear broken
On user-initiated retry or regeneration, either \(a\) automatically increase temperature slightly \(e.g., 0 to 0.3-0.5\), \(b\) append a hidden random seed or variation instruction to the prompt, or \(c\) prompt the user to rephrase their input before retrying. Never silently re-submit the identical request with identical parameters.
Journey Context:
When a user clicks 'retry' or 'regenerate,' they expect a different result. But with temperature=0 \(deterministic mode, which many production systems use for consistency and reproducibility\), the same prompt produces byte-identical output every time. The user watches the AI 'try again' and produce the exact same wrong answer, which feels broken rather than uncertain. Teams set temperature=0 for reliability and then add a retry button without realizing the contradiction. The fix requires a design decision: varying generation parameters on retry trades some consistency for variety; prompting the user to rephrase trades ease for better outcomes. The hidden-variation approach \(appending a random token like 'Approach this differently: variation 7'\) is a practical middle ground but can produce unpredictable quality shifts. For code generation specifically, temperature variation is safer because syntax constraints limit how wrong the output can get.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:32:53.782321+00:00— report_created — created