Every RAG tutorial ends at the same place: chunk the documents, embed the chunks, insert the vectors, ask a question. That is day one. On day two someone edits a document, and nothing in the tutorial tells you what to do. This post walks through the nine problems that show up after that, in the order you usually hit them. Each fix solves one problem and exposes the next. You can replay all nine in a browser lab I added to my Advanced Local RAG demo .

Why this is the hard part

Building a retrieval pipeline is a weekend project. Running one is not, because the corpus is never finished. Policies change, a typo gets fixed, a product gets renamed. Every one of those edits has to reach the vector index correctly, cheaply and without users noticing .

Most of the failures below share one dangerous trait: nothing errors . There is no exception and no alert.…