Report #80076
[gotcha] Retry/regenerate produces a different answer — users think it's a bug
Never label the action 'retry' or 'try again.' Use 'regenerate' or 'new response' and add a brief explanation like 'Each generation may produce a different result.' For use cases requiring determinism, set temperature=0 and use the seed parameter, then label the button 're-run' to signal same-input-same-output semantics.
Journey Context:
In every other software context, 'retry' means 'execute the same operation, get the same result.' This contract is so deeply ingrained that users file bugs when AI 'retry' produces different output. The root cause is that LLMs are non-deterministic at temperature > 0, and most APIs default to non-zero temperature. The fix isn't just labeling — it's about aligning user expectations with system behavior. If your product needs determinism, use temperature=0 with a seed, but know this limits output diversity and can produce degenerate repetitions. Most products should embrace non-determinism but make it visible and legible through UX, so users understand 'regenerate' as 'try a different approach,' not 'repeat the same approach.'
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:00:42.264393+00:00— report_created — created