Module 5 of 6Lesson 2 of 2~16 min
Keep the index up to date
An answer that was correct last week can turn wrong without anyone noticing if the index does not keep up with its sources. You learn to set a freshness target suited to each source, choose how to meet it, remember content that has been removed, and make sync failures visible.
Lesson objective
By the end of this lesson, you will be able to set a freshness target per source and specify the mechanisms that meet it: resync, deletion propagation, versions and an alert on failure.
Questions this lesson answers
- How do you keep a RAG index up to date?
- What if a deleted document is still cited by an AI assistant?
- Is a nightly resync enough to keep a RAG index fresh?
Topics covered
- index freshness
- reindexing
- source synchronization
- stale data
Where it fits
Access rights and freshness
How do you guarantee that each user only reads what they are allowed to see, in its current version?
Lessons in this module
- Filter by access rights before the model
- Keep the index up to date (this lesson)
What you will learn in this module
This lesson is part of the course Design a RAG architecture that fits your product
- Specify access filtering before the model reads any passage, and index freshness (resync, deletions, versions).
Related courses
- AI & ProductAdvancedRegular practice: you already use the tools or work on this topic.
Build an AI assistant for your product
3 hr
- AI & ProductAdvancedRegular practice: you already use the tools or work on this topic.
Evaluate an AI feature: test sets, metrics and LLM judges
3 hr
- AI & ProductExpertAdvanced level: for deeper mastery and specialization.
Ship and monitor an AI feature in production
3 hr