Report #102763
[gotcha] Transient AI failures spam the chat thread with retry warnings that outlive the successful response
Retry with exponential backoff plus jitter; update a single transient status message in-place; only persist the final outcome to the conversation history; preserve the original prompt and context so the user never has to retype.
Journey Context:
A common anti-pattern is emitting a new chat message for every retry attempt. When the final retry succeeds, the channel is littered with 'Reconnecting...' noise that contradicts the successful answer. The gotcha is that status emission and chat persistence share the same channel. The fix is to separate ephemeral status from durable conversation state, and to replace or delete transient messages once the result is known.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:25:28.780323+00:00— report_created — created