AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 4 November 2026

Can Dify handle conflicting retrieved sources?

Dify flagged conflicting warranty terms rather than choosing one as fact. It retrieved documents stating 24 months and 36 months from delivery and included both periods in its answer.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Two documents give different values for the same factPassEvidence
What we sent

“What is the warranty period on a new Tolvan A3?”

What the tool returned
Text
I’m not sure—some versions list 24 months and others 36 months from the delivery date. Could you share your purchase date or the warranty terms/version from your sales pack so I can confirm the correct period for your instrument?

Request and response log: the same exchange with the app settings appended

Copied from Captured file (text), line 20

Open the text file ↗
Expected vs. Found
✓Expected: Convey that the retrieved sources disagree, without presenting either warranty period as the definitive fact.Found: The conflicting documents ranked first and second, stating 36 and 24 months from delivery; the answer named both periods and chose neither.
Supporting proof
Proof 1Screenshot
Notebook screenshot: the same answer and four retrieval scores
Open original ↗
Why this result

An uncertain answer alone would not establish that Dify recognized conflicting sources: both documents had to be retrieved. Dify retrieved both and acknowledged their disagreement without treating either warranty period as settled fact.

Also observed in this test case

Suggested clarification. For the warranty question, Dify asked for the customer's purchase date or the warranty version in the sales pack to help resolve the disagreement.

Unrelated interval left out. The third-ranked sales-pack passage gave no warranty figure. The fourth-ranked product overview gave an unrelated 22-month recalibration interval, which did not appear in the answer.

Tested by Vivek Tomar · evidence dated 21 September 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
Dify
Build or version
Not captured in this run
Model
gpt-5 (Chat mode)
Surface
API
Set up before the run
Two Tolvan A3 warranty documents had to give different warranty periods, with no date or version marker indicating which superseded the other.
Retrieval strategy
multi-path retrieval
Reranking
Weighted Score -- Semantic 1.0 / Keyword 0.0
Top K
4
Score threshold
disabled
Response mode
blocking
Tested
21 September 2026 · Vivek Tomar

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

LevelNameScope
BenchmarkManaged RAG →15 scenarios · 9 tools
CapabilityGrounded Generation →
ScenarioThe retrieved sources disagree with each other →
ToolDify →

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
16 November 2026First publishedManaged RAG v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/managed-rag/results/dify/conflicting-sources · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-04

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Same content as Captured file ↗text/plain; charset=utf-8 · 6 KB
Captured file (text) ↗text/plain; charset=utf-8 · 7 KB
Proof 1 · Screenshot ↗image/png · 185 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Same content as Captured file6159a70de910a86d74e64421880b5b1e9d9bb9682ae3e482be2012b8182bee17
Captured file (text)f1118496f6678dd20d7bebeb54cd9ecfaf35d2d2846e857940b13211cbf42b63
Proof 1 · Screenshotfdd13016bff66520ba56f775982c6aad58d8b07e04feb87f97caf1421c6a50fa