Symptom
When SummarizationMiddleware's summary call fails, the conversation history is deleted and the error text is stored as the summary.
Evidence what you'll see
- The summary message contains an error string
- Earlier messages are gone from state
Cause
The summary step caught the exception and turned it into a fake summary, which then replaced the history as if it were real.
Fix steps
0 of 1 done
Your check marks stay in this browser only.
Verify the fix worked
- Force the summary call to fail and confirm an error is raised and the original messages remain.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it