State Pollution
A data contamination problem caused by improper shared state management among plugins or modules. It occurs commonly in cross-session components such as memory plugins, and may persistently affect subsequent tasks without producing explicit errors.
Timeline (last 90 days)
In multi-step agentic systems based on LangGraph, abnormal intermediate steps, tool call failures, or unexpected model outputs may cause incomplete or incorrect data to be written into the memory state, which is known as state contamination.
Contaminated state continues to be read and accumulated in subsequent steps, forming a snowballing error effect.
Silent errors caused by state contamination are harder to diagnose than direct crashes, because the system appears to be running while its output quietly deviates from the correct direction.
All Facts (3)
In multi-step agentic systems based on LangGraph, abnormal intermediate steps, tool call failures, or unexpected model outputs may cause incomplete or incorrect data to be written into the memory state, which is known as state contamination.
50%UnverifiedContaminated state continues to be read and accumulated in subsequent steps, forming a snowballing error effect.
50%UnverifiedSilent errors caused by state contamination are harder to diagnose than direct crashes, because the system appears to be running while its output quietly deviates from the correct direction.
50%