Demo: a stale policy answer fixed by event-driven re-indexing
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
show a stale answer, trace it in the logs, and fix it with a re-index event.
Draft outline details
Step by step
- Ask "How many days do I have to return an item?" and get the old 14-day answer after the policy changed to 30 days.
- Read the logs: the cited chunk id and its
updatedtime show the stale chunk was retrieved; the model was right to use it. - Publish
HelpArticleUpdatedfor the article; the consumer re-chunks, hash-compares, and re-embeds only changed chunks. - Planned mistake: the consumer inserts new chunks but forgets to delete old ones, so both answers are retrieved. Fix: replace the article's chunks in one transaction.
- Ask again; the answer shows 30 days within one minute; confirm the unchanged articles were not re-embedded.
- This prepares the freshness criterion of
MID-068-LAB1.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.