Why does RAG fail when my question doesn't match the wording of the source document?

RAG retrieval works by embedding the question and comparing it to embedded chunks of the corpus, and embedding similarity tracks meaning loosely, not exact wording. A chunk that answers the question in different words, a synonym, a different verb, an abbreviation the corpus never spells out, can sit far enough from the question’s embedding that it never makes the top results, even though it holds the right answer. This is a retrieval failure, not a generation one: the model never saw the chunk, so no amount of prompting fixes it. Keyword search doesn’t share the weakness, since it matches literal terms, which is why production systems that hit this problem usually add a keyword pass alongside the vector one and merge the two rankings rather than trusting embeddings alone. If an answer consistently misses information you know is in the corpus, check what the retrieved chunks actually were before assuming the model reasoned badly.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y