RAGEngineering Hub

Fix Finder

What are you seeing?

Builders arrive with a problem, not a topic. Pick the symptom, do the first check, then read the pages that explain the cause and the fix.

Numbers from tables come out wrongingestion

First check

Look at the parser output for that table before blaming retrieval.

Read

The answer is only half rightrepresentation
An exact code or product ID is never foundretrieval

First check

Run a keyword (BM25) search for the code on its own.

Read

The right document is found but ranked too lowretrieval

First check

Compare the rank before and after reranking.

Read

Follow-up questions failretrieval

First check

Log the rewritten query the system actually searched with.

Read

The model ignores the retrieved contextgeneration

First check

Check that the right chunk was really in the prompt.

Read

Answers come from an old versioningestion

First check

Check the document version and the indexed date of the chunk used.

Read

Users see documents they should notdeployment

First check

Check that the access filter ran on every query, not only some.

Read

Responses are too slowdeployment

First check

Time each stage separately: retrieval, reranking, generation.

Read

Each answer costs too muchdeployment

First check

Count tokens per query and see where they go.

Read

You cannot tell if a change made it betterevaluation