Report #88302
[gotcha] Retrying a failed LLM prompt with the previous failed response still in conversation history causes the model to reproduce similar failures
Before retrying, either remove the failed assistant response from the conversation history, or prepend a system message marking it as unsatisfactory \(e.g., 'The previous response was inadequate. Provide a different approach.'\). Never retry with the failed response silently remaining in context.
Journey Context:
When an AI response is unsatisfactory and the user retries, many implementations keep the failed response in the conversation history. This poisons the retry: the model sees its own failed output as part of the context and tends to produce similar outputs due to in-context anchoring. Even worse, if the failure was a refusal, the model may see its own refusal as a precedent and refuse again with even more conviction. The fix options are: \(1\) remove the failed response from context before retrying \(cleanest but loses conversation continuity\), \(2\) add a system message marking the previous response as unsatisfactory \(preserves continuity while signaling a different approach is needed\), or \(3\) start a fresh context for the retry with only the original prompt. Option \(2\) is often best because it preserves conversation continuity while explicitly breaking the anchoring effect. The key insight from in-context learning research: LLMs are strongly influenced by their own prior outputs in context — a failed response in history is not neutral, it is an anchor that biases future generation toward similar failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:47:52.138712+00:00— report_created — created