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

Does RAGFlow report when an uploaded file cannot be processed?

RAGFlow did not flag the two unreadable uploads as document failures. A truncated PDF and a password-protected PDF received the same success status as a readable comparison document.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

Unprocessable file submitted through the normal upload pathFailEvidence
What we sent

We uploaded a readable comparison document, a truncated PDF and a password-protected PDF, then started parsing through RAGFlow’s API.

What the tool returned

Only the tool's reply to inputs 1, 2 and 3 is copied here; its reply to input 4 was not copied as text. The rest of what the tool returned is shown in the evidence under Proofs.

Text
{'run': 'DONE', 'status': '1', 'progress': 1.0, 'chunk_count': 0, 'token_count': 0, 'size': 2114, 'process_duration': 9.9354}

API response log: comparison document, repeated ingestion statuses, stored copies and retrieval results

Copied from Captured file (text), line 43 · an excerpt

Open the whole text file ↗
Everything the tool returned, in order (5)
  1. Truncated PDF status

    {'run': 'DONE', 'status': '1', 'progress': 1.0, 'chunk_count': 0, 'token_count': 0, 'size': 2114, 'process_duration': 7.49227}

  2. Password-protected PDF status

    The final response, printed above.

  3. Truncated PDF ingestion log

    11:51:22 Page(1~2): No chunk built from bad_01_truncated.pdf

  4. Password-protected PDF ingestion log

    11:51:24 Page(1~2): No chunk built from bad_02_password_protected.pdf

  5. Good control document status

    {'run': 'DONE', 'status': '1', 'progress': 1.0, 'chunk_count': 2, 'token_count': 567, 'size': 2775, 'process_duration': 3.72094}

Source excerpt · partial file · response 3

Text
11:51:22 Page(1~2): No chunk built from bad_01_truncated.pdf
11:51:22 Page(1~2): Task done (6.01s)

Copied from Captured file (text), lines 36–37 · an excerpt

Source excerpt · partial file · response 4

Text
11:51:24 Page(1~2): No chunk built from bad_02_password_protected.pdf
11:51:24 Page(1~2): Task done (9.01s)
uploaded bytes: 174963 | stored bytes: 2114
stored copy head: b'%PDF-1.7\n%\xc7\xec\x8f\xa2\n%%Invocation: gs ? ? -sDEVICE=pdfwrite -dPDFS' | length 2114 | contains Ghostscript: True
scoped retrieval probe: code 0 chunks 0

Copied from Captured file (text), lines 52–56 · an excerpt

Expected vs. Found
✗Expected: Report a failure for each document that cannot be processed.Found: Both PDFs were marked successfully completed with zero chunks, including in the existing dataset. Failure appeared in free-text progress messages, not as a document failure status.
Supporting proof
Proof 1Screenshot
Notebook screenshot: upload, parsing and reported success with zero chunks for the truncated PDF
Open original ↗
Proof 2Screenshot
Notebook screenshot: upload, parsing and reported success with zero chunks for the password-protected PDF
Open original ↗
Why this result

Both unreadable PDFs received success rather than failure statuses. A readable comparison document produced 2 chunks through the same upload and parsing path, so this is a reporting failure, not an execution failure. This conclusion covers REST API status; the web console’s document list was not inspected.

Also observed in this test case

Stored rewrite. Both unreadable uploads were stored as 2,114-byte Ghostscript rewrites, and neither the status nor the response said the original file had been replaced.

Zero-chunk retrieval. A retrieval probe for each unreadable file returned success with zero chunks, so neither file contributed retrievable content.

Failure state exists. The product can return a failure state on this path, but these uploads did not receive it.

Tested by Vivek Tomar · evidence dated 22 October 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
RAGFlow
Build or version
v0.26.4
Plan or tier
Starter
Surface
API
Set up before the run
A truncated PDF and a password-protected PDF had to be submitted through the normal upload-and-parse path, then their ingestion statuses read. The attempt was repeated in a fresh dataset with a readable comparison document.
Ingestion path
POST to the dataset documents endpoint, then POST to the dataset chunks endpoint
Tested
22 October 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
CapabilityData Ingestion →
ScenarioA bad file in the upload →
ToolRAGFlow →

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
13 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/ragflow/a-bad-file-in-the-upload · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-22

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.

Proof 1 · Screenshot ↗image/png · 188 KB
Proof 2 · Screenshot ↗image/png · 188 KB
Captured file (text) ↗text/plain; charset=utf-8 · 4 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshot95bf4d7c672c839a2c55af2c830e68dcb30c33ff224ed552168e3dfbe040782f
Proof 2 · Screenshot1e274282794ad136699ecf165f29ba846ef75d70981388d9659800a0cfb77726
Captured file (text)209f470ef39f87ecf6f835aed43ed0811d34e5222f92200f2d53af2d0bb1c41d