docs: add quick RAG triage checklist to RAG troubleshooting page#1112
Open
onestardao wants to merge 1 commit intoopen-webui:mainfrom
Open
docs: add quick RAG triage checklist to RAG troubleshooting page#1112onestardao wants to merge 1 commit intoopen-webui:mainfrom
onestardao wants to merge 1 commit intoopen-webui:mainfrom
Conversation
Added a Quick RAG Triage Checklist to assist users in diagnosing common issues with RAG responses. Expanded explanations and solutions for various RAG-related problems.
ℹ️ Documentation PR Guidelines👋 Welcome! This is an automated message posted on all new documentation PRs to help guide our contributors. Just because this comment appeared doesn't mean you have done anything wrong! Please ensure you're using the correct branches: Target branch (where you're merging TO):
Source branch (where you're merging FROM):
If your docs PR depends on a pending PR in open-webui/open-webui:
Please adjust your PR target branch, source branch, and/or draft status accordingly if needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
this PR adds a small “Quick RAG Triage Checklist” section to the existing RAG troubleshooting page. it gives users a symptom first table that maps what they observe to the most likely failure area, and points them to the relevant sections already documented on the same page.
Why
RAG issues are often reported as “hallucination” but the root cause is usually context side: ingestion, extraction, chunking, embeddings, retrieval, or context window limits. a short triage table helps users and maintainers converge faster, reduces repetitive support threads, and improves the signal quality of bug reports.
What changed
added a single section near the top of the RAG page:
Quick RAG Triage Checklist
a compact table (P01–P12) mapping symptom to likely pattern and which section to read first.
no other docs changes.
Scope
docs only
one file changed: docs/troubleshooting/rag.mdx
Testing
docs build not run locally in this PR (content only change)
no runtime behavior changes