Report #24751
[gotcha] Retrying after an AI refusal in the same conversation increases subsequent refusal rates
On retry after a refusal, strip the refused exchange from conversation history or start a fresh context. If preserving context is necessary, prepend a system message acknowledging the refusal was likely a false positive and permitting the category of request.
Journey Context:
When a model refuses a request, the refusal and its reasoning enter the conversation history. On retry, the model sees its own prior refusal as context, making it more conservative — a refusal cascade. Developers assume retrying is neutral because the user rephrased, but the model interprets the history as 'I already decided this was inappropriate.' The counter-intuitive fix: starting fresh feels like losing state, but it actually improves success rates for legitimate rephrased requests. This is especially painful in coding tools where a false refusal on a security-related query poisons all subsequent queries in the session.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:57:29.485947+00:00— report_created — created