Report #64365
[gotcha] Retrying a refused AI prompt without modification produces the same refusal in a frustrating loop
When displaying a refusal, do not offer a bare 'retry' button. Instead, offer 'rephrase' with a suggested modified prompt, or surface which part of the input likely triggered the refusal so the user can edit meaningfully. If you must include retry, modify the prompt under the hood \(e.g., prepend a rephrasing instruction\) rather than resending verbatim.
Journey Context:
The intuitive UX mirrors traditional software: error → retry. But AI refusals are near-deterministic for the same input. Identical prompts produce identical refusals. Users click retry 3–5 times, get the same result, and conclude the system is broken. The frustration compounds because each retry has full latency cost. The counter-intuitive fix: remove the standard retry pattern entirely. This feels wrong — you're taking away the user's primary recovery action — but a retry that is guaranteed to fail is worse than no retry at all. Guided rephrasing has a higher interaction cost but a dramatically higher success rate.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T14:31:38.903747+00:00— report_created — created