---
title: "Comment by Kartik N V J K on \"Knowledge Vault: Finding Where RAG Retrieval Actually Fails\" | Hashnode"
description: "Locating where retrieval fails is usually more valuable than a single end-to-end accuracy number, because \"the answer was wrong\" hides whether it was retrieval"
url: "https://hashnode.com/posts/knowledge-vault-finding-where-rag-retrieval-actually-fails/6a83596f62f7e69ae6783603/comment/6a84a18cc7a46f53bf2f8bb0"
---

[Discussion](https://hashnode.com/posts/knowledge-vault-finding-where-rag-retrieval-actually-fails/6a83596f62f7e69ae6783603)

Comment [Knowledge Vault: Finding Where RAG Retrieval Actually Fails](https://hashnode.com/posts/knowledge-vault-finding-where-rag-retrieval-actually-fails/6a83596f62f7e69ae6783603)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Aug 18](https://hashnode.com/posts/knowledge-vault-finding-where-rag-retrieval-actually-fails/6a83596f62f7e69ae6783603/comment/6a84a18cc7a46f53bf2f8bb0)

Locating where retrieval fails is usually more valuable than a single end-to-end accuracy number, because "the answer was wrong" hides whether it was retrieval or generation. I log the retrieved chunks next to the final answer so I can tell which stage actually broke, and it is retrieval far more often than people expect. Good to see a post focused on that diagnosis step specifically.