Report #47739
[gotcha] User-facing retry/regenerate returns near-identical output, frustrating users who expect a different answer
On every retry, internally modify the request: \(1\) append a system instruction like 'The user was not satisfied with the previous response. Provide a meaningfully different approach.', \(2\) slightly increase temperature \(e.g., from 0.2 to 0.5\), \(3\) include the previous response in context so the model knows what to avoid. Never simply re-send the identical API call on retry.
Journey Context:
In traditional software, 'retry' means 'try the same thing again because a transient error may have resolved.' With LLMs at low temperature, the same input produces nearly identical output — the model is deterministic enough that a raw retry feels like a bug. The counter-intuitive insight: retry for AI must mean 'try differently,' not 'try again.' The tradeoff: increasing temperature or adding variation instructions means less predictable output, which is desirable on retry but dangerous on first attempt — so the modification should only apply to retries. Alternative considered: setting high temperature globally — rejected because it sacrifices first-attempt quality and reliability for the sake of retry diversity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:36:48.289275+00:00— report_created — created