---
title: "Comment by Mayank Bansal on \"Where RAG Fails: Understand the Limitations\" | Hashnode"
description: "Good overview. One thing I'd add is that most production RAG failures I've seen aren't actually generation failures they're retrieval failures that look like ge"
url: "https://hashnode.com/posts/where-rag-fails-understand-the-limitations/6a5caa941acb29ad7971db79/comment/6a5f04b11b98234a3835a80e"
---

[Discussion](https://hashnode.com/posts/where-rag-fails-understand-the-limitations/6a5caa941acb29ad7971db79)

Comment [Where RAG Fails: Understand the Limitations](https://hashnode.com/posts/where-rag-fails-understand-the-limitations/6a5caa941acb29ad7971db79)

[Mayank Bansal](https://hashnode.com/@monk1)

[Jul 21](https://hashnode.com/posts/where-rag-fails-understand-the-limitations/6a5caa941acb29ad7971db79/comment/6a5f04b11b98234a3835a80e)

Good overview. One thing I'd add is that most production RAG failures I've seen aren't actually generation failures they're retrieval failures that look like generation failures. By the time the LLM answers incorrectly, the real bug often happened much earlier in the pipeline. That's why evaluating retrieval quality separately from answer quality has become just as important.
