The Scenario
A customer support agent is helping a user reset their password. The agent accidentally tries to update anull field, causing the LLM to get confused and start repeating “I’m sorry, I can’t do that” in a loop.
1. Detection
In your application logic, you detect that the last 3 outputs have been nearly identical.2. The Rollback
Instead of killing the session, you simply roll the session state back to the turn before the error occurred.Why this matters
- Save Revenue: You don’t lose the user’s progress. They don’t have to start the 10-minute onboarding over again.
- Traceability: In the Dashboard, you’ll see a “Rollback Event,” allowing your developers to analyze the exact turn that caused the drift.
- User Experience: The user sees a slight delay followed by a successful answer, rather than a “System Error” message.