Pain map
What breaks in document AI
290 production incidents from public threads. Every quote links to its source. Pick a category and check it yourself.
Missing documents and recall
18 of 18 quotes
“Chat refuses with “available sources are insufficient” even when retrieval and the thought trace contain the answer”
GitHub, ragflow · 13 October 2026 · open the thread “If all retrieved chunks are timetables, the LLM can't answer even though the correct information exists in the knowledge base.”
Reddit, r/Rag · 3 August 2026 · in production · open the thread “the system might return no results or only IDs 1 and 5, falling far short of the actual ten.”
GitHub, ragflow · 20 July 2026 · open the thread “A large subset of matching documents are excluded from retrieval.”
GitHub, ragflow · 1 July 2026 · open the thread “I found that when I upload a large number of documents to the knowledge base, the AI sometimes cannot retrieve all the relevant content, so its answers may be incomplete.”
LangChain forum · 15 June 2026 · in production · open the thread Hit this one too? We are building for it.
“The retrieved chunks are relevant to the query but miss necessary details spread elsewhere.”
LangChain forum · 28 May 2026 · open the thread “The main issue was that answers were obvious in the documents but the system was just not retrieving them in a reliable way.”
Reddit, r/Rag · 7 May 2026 · in production · open the thread “Top-1 hit rate sat around 60% on our eval set, which sounds fine until you realize the wrong 40% was the system confidently returning similar-but-wrong documents on policy questions.”
Reddit, r/Rag · 29 April 2026 · in production · open the thread “"Total unpaid invoices from last quarter": a vector search returns chunks from random documents, not an answer.”
Reddit, r/Rag · 27 April 2026 · in production · open the thread “the questions they would like to ask are very... broad? Like "How many Xs have Y". Stuff that would require a human to review almost every document.”
Reddit, r/Rag · 9 April 2026 · in production · open the thread “The system retrieves semantically relevant content about the entity, but fails to prioritize results within the intended time window, even when increasing K.”
Hugging Face forum · 24 March 2026 · in production · open the thread “It pulls the completely wrong documents”
Reddit, r/Rag · 4 March 2026 · in production · open the thread “the performance in recall testing shows that correct results are ranked relatively low; the same issue occurs in actual usage.”
GitHub, ragflow · 28 January 2026 · open the thread “In several cases, Ragflow does not surface information that we know exists in the underlying documents.”
GitHub, ragflow · 28 January 2026 · in production · open the thread “the amount of data synchronized in the ragflow is different from that of the original data.”
GitHub, ragflow · 20 January 2026 · open the thread “It is functional at RAG stuff on internal docs but definitely not good - not sure how much of this is Copilot vs corporate disarray and access controls.”
Hacker News · 4 December 2025 · in production · open the thread “When we first built our RAG, it showed promising results (around 90% recall on large knowledge bases). However, when the first actual users tried it, it could barely answer anything (closer to 30%).”
Hacker News · 28 November 2025 · in production · open the thread “chunks from documents 31+ do not contain `document_metadata`.”
GitHub, ragflow · 26 November 2025 · open the thread Hit this one too? We are building for it.
Method
We collected 448 public posts published after 1 November 2025 in which a builder describes document AI failing. Each link was re-opened on 8 November 2026. We kept the 290 where the quote is on the page, the author describes an incident and not an opinion, and has no tie to a vendor. Quotes are verbatim and trimmed after 420 characters. The grouping is ours. A complaint is not a measurement.