Observed arrival · 2026-11-18
ChunkTrace finds where a RAG answer went missing
A RAG retrieval profiler replays a query trace to identify where a needed chunk was lost and suggest what to change.
- For
- RAG developers debugging retrieval failures
- Worth noticing
- Its example traces `refund-policy#2` at rank 2, shows `top_k=1` cutting it, then demonstrates the change to `top_k=4`.
Field notes
The illustrated trace records counts as a query moves through index, filter, threshold, top_k, rerank, context, and generation. In the refund example, the page gives the dropped chunk’s rank and the relevant `top_k` value, then shows the answer appearing after the setting changes. ChunkTrace also distinguishes cases where the trace cannot establish a cause: it names `NO_LABEL` and `SHADOW_MISSING` as limits, and says `UNEXPLAINED_EXCLUSION` can flag a chunk that should have been returned but was not.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue