# RAG Index Freshness and Reindexing
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

RAG index freshness is the gap between the source corpus and the searchable retrieval index; reindexing is the process that closes that gap after content changes.

## Core Explanation

A RAG system can cite stale facts when documents change but embeddings, metadata, or vector records are not updated. Freshness work includes detecting changed documents, updating records by stable IDs, handling deletions, and knowing when an embedding-model or chunking change requires a wider rebuild.

Agents should expose index freshness as evidence. If a retrieved document is old or the index has not caught up with a source update, the agent should say so rather than presenting stale retrieval as current truth.

## Source-Mapped Facts

- LlamaIndex document management documentation describes tracking document hashes to determine whether documents have changed. ([source](https://developers.llamaindex.ai/python/framework/module_guides/indexing/document_management/))
- Pinecone documentation says upsert writes records into a namespace and overwrites existing records with the same ID. ([source](https://docs.pinecone.io/guides/index-data/upsert-data))
- Weaviate documentation describes updating existing objects by object ID. ([source](https://docs.weaviate.io/weaviate/manage-objects/update))

## Further Reading

- [LlamaIndex Document Management](https://developers.llamaindex.ai/python/framework/module_guides/indexing/document_management/)
- [Pinecone Upsert Data](https://docs.pinecone.io/guides/index-data/upsert-data)
- [Weaviate Update Objects](https://docs.weaviate.io/weaviate/manage-objects/update)