Report #70093
[gotcha] Retry button on AI refusal produces identical refusal frustrating users
When the AI refuses a request, do not offer a generic 'retry' or 'regenerate' button. Instead, display the refusal reason, suggest how to rephrase the prompt, and provide an editable input field so the user can modify their request before resubmitting. If you must include a retry, modify the system message or add context acknowledging the previous refusal to increase the chance of a different outcome.
Journey Context:
Standard web UX teaches: error → retry button → success. But AI refusals are near-deterministic for the same input — the same prompt will produce the same refusal. Users click 'retry' repeatedly, each time getting the same rejection, each time getting more frustrated. The system appears broken or stubborn. The fix inverts the standard pattern: instead of 'try the same thing again,' the UX must guide the user toward 'try a different thing.' This means refusals need their own UI treatment distinct from transient errors — explanation plus rephrasing guidance, not a retry loop. The counter-intuitive part is that the correct UX for an AI refusal is the opposite of the correct UX for a network error.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:14:05.010286+00:00— report_created — created