Report #53607
[gotcha] Retrying an AI refusal with the same prompt keeps producing the same refusal but users keep clicking retry
When a refusal occurs, do not offer a simple 'retry' button that resends the identical prompt. Instead, offer guided reformulation: suggest how the user might rephrase, explain which part of the request triggered the refusal, or automatically adjust the prompt framing. If you must offer retry, add temperature variation and a prompt prefix that shifts the context.
Journey Context:
When an AI refuses a request, it is almost always because the prompt triggered a safety or policy threshold. Sending the exact same prompt will almost always trigger the same threshold, producing the same refusal. Yet most retry UX just resends the identical request, wasting time and frustrating users who think 'maybe it will work this time.' This is especially pernicious because LLM refusals have some stochasticity — occasionally the same prompt does get through on retry due to sampling variance, which reinforces the gambling behavior and undermines safety boundaries. The deeper issue is that refusals are not transient errors — they are policy decisions. Treating them like network failures \(just retry\!\) is a category error. The right fix is to treat refusals as a distinct UX flow: explain what happened, offer alternatives, and help the user reformulate. The tradeoff: this adds complexity to the refusal flow, but the alternative is a frustrating loop that teaches users to spam retry until they get through, which defeats the safety system.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:28:36.324716+00:00— report_created — created