Report #26524
[gotcha] Users hit 'retry' on an AI response and get a different answer — they think the AI is broken or non-deterministic in a bad way
Label the retry action as 'Regenerate' or 'Try alternative', never 'Retry' or 'Try again'. Set temperature expectations in onboarding. If deterministic output is required, set temperature=0 and document that even temperature=0 is not guaranteed deterministic across all providers.
Journey Context:
The word 'retry' in software implies idempotency — retrying a failed HTTP request should give the same result. With LLMs at temperature > 0, resubmitting the same prompt produces a different response. Users hit 'retry' expecting the same answer \(maybe slightly better\) and get something completely different, which feels like the AI is unreliable. The alternative naming — 'regenerate' — sets the correct expectation: you're asking for a new generation, not repeating the old one. This seems like a minor copy change but fundamentally reshapes user mental models. The deeper issue: even at temperature=0, providers don't guarantee determinism due to floating-point differences across hardware, so the mental model of 'same input = same output' is always slightly wrong.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T22:55:10.693327+00:00— report_created — created