Your RAG system cites a document you already replaced

Support changed the return policy last week and my RAG bot is still quoting the old one.

Intermediate to advancedRead 5 minDoing: an afternoon, once your ingestion script can already add and delete records by id7 steps

▶ Start

What you'll have at the end

A RAG answer that quotes this week's return policy, with every chunk from the retired version gone from the index instead of merely outranked.

Before you start

You need

A RAG pipeline that already chunks, embeds, and inserts documents into a vector store whose records you can also delete, by id or by a metadata filter.

Not covered

Detecting that a source document changed in the first place, through a webhook or a content-management alert; this starts from already knowing an edit happened.

Leans on

7 steps

Where to go next

Your RAG's retrieval hit rate has never been measured

when you want an ongoing number for retrieval quality overall, not confirmation that this one document is fixed

Checked 15 Aug 2026

Part of the RAG (Retrieval Augmented Generation) cookbook