Report #24546
[synthesis] Agent confidently outputs outdated information because the vector store contains stale documents with high similarity scores
Implement recency weighting in retrieval and monitor the age distribution of retrieved chunks; flag answers derived from documents older than a threshold.
Journey Context:
Vector databases return results based on semantic similarity, not recency. If a policy changes \(e.g., API deprecation\), the old documentation might still have higher semantic similarity to the query than the new docs. The agent retrieves the old doc, answers confidently, and the user gets bad code. No errors are thrown. You must instrument the metadata \(timestamp\) of retrieved chunks and track the freshness of agent context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:36:33.857640+00:00— report_created — created