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

Does Denser AI flag an unprocessable upload as failed?

Denser AI reported an unreadable truncated PDF as ready rather than flagging its failure. It did flag a password-protected PDF as failed in the same upload.

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 truncated PDF and a password-protected PDF through Sources, Add source, Upload files in Denser’s dashboard. We then read the source statuses and opened the truncated PDF’s preview and passages tabs.

InputDocument (PDF)
Input PDF: the truncated document
Open the PDF ↗
What the tool returned

The tool's response has no text to quote: it is what the evidence under Proofs shows.

Proof 3 · Screenshot

Proof 2 · Screenshot

Proof 1 · Screenshot

Expected vs. Found
✗Expected: Report a failure for the document that cannot be processed.Found: Denser’s viewer could not display the truncated PDF and its reading tab contained no passages, yet its source status was ready.
Supporting proof
Proof 1Screenshot
Sources screenshot: truncated PDF marked ready and password-protected PDF marked failed
Open original ↗
Proof 2Screenshot
Preview screenshot: the truncated PDF cannot be displayed
Open original ↗
Proof 3Screenshot
Screenshot: the truncated PDF’s empty passages tab
Open original ↗
Proof 4Captured file (text)
Test notes: the initial upload and the repeat attempt
Text52 lines
=== TC89 -- bad-file ingestion status (UI only, no API query involved) ===

Fixture: bad_01_truncated.pdf (deliberately truncated/corrupt PDF, upload-only fixture set)
Chatbot: R6-stable-SS-v1 (same chatbot as TC86-88, 9th source added on top of the 8-doc stable slice)
Uploaded via: Sources > Add > Files > Choose files (dashboard UI, no ingestion API exists on this
tool per reference/api-denser.md)

--- Step 1: upload ---
File uploaded, size reported 87.77 KB. Immediate post-upload UI optimistically rendered row as
"Trained" before the "Uploading 1 file..." notification had even cleared.

--- Step 2: confirm post-refresh (not just an optimistic client-side render) ---
Clicked "Refresh sources" explicitly, re-read the Sources table.
Result: bad_01_truncated.pdf | Status: Trained | Hits: 0 | Size: 87.77 KB
Identical status styling (green dot, "Trained" label) to all 8 genuine, successfully-ingested
documents in the same table -- no distinct warning/error/partial/failed state of any kind.

--- Step 3: attempt to preview the file inside Denser's own PDF viewer ---
Clicked the source row to open Preview.
Result: "Unable to load PDF -- The file may have been moved or deleted."
This is Denser's own UI being unable to open the exact file it has simultaneously marked
"Trained" in the Sources table (visible in the same screenshot, side by side -- see
tc89-02-bad-file-preview.png).

--- Conclusion ---
Denser's ingestion pipeline reports a truncated, unparseable PDF as a fully successful "Trained"
source -- the same status given to every genuinely ingested document -- with no failure signal
anywhere in the dashboard. The product's own preview feature cannot open the file, directly
contradicting the "Trained" status shown one UI panel over. This is the TC89 failure mode exactly
as specified: "a per-document FAILURE status for that file... Reporting success -- or reporting
nothing -- is the failure."

--- Second ingestion, 17 November 2026 (truncated file and a password-protected file) ---
The original 9-source chatbot no longer exists (Free plan allows one agent), so both files were
uploaded to the remaining agent, R6-mutation-MS-v0 (4 other files, 6 sources in total), via
Sources > Add source > Upload files. The dashboard now labels sources "Ready" / "Failed"
instead of "Trained".

bad_02_password_protected.pdf | 171 kB | Status: Failed | "document closed or encrypted. To try again,
  delete it and add it again."  -> failure reported
bad_01_truncated.pdf          |  88 kB | Status: Ready  | same green badge as the good files
  -> failure NOT reported
  - Preview (File tab): "Can't show this file"
  - "What the agent read" tab: "No passages yet" (nothing was read from the file)

So Denser does have a Failed state and uses it for the encrypted file, but still marks the truncated
file Ready although nothing could be read from it. Verdict unchanged: Fail.

Screenshots (17 Nov 2026 ingestion; the 5 Oct 2026 first-run screenshots are no longer kept):
- tc89-03-sources-status-annotated.png -- Sources list, password-protected file Failed, truncated file Ready
- tc89-04-truncated-preview-fails-annotated.png -- Denser's viewer on the truncated file: "Can't show this file"
- tc89-05-truncated-nothing-read-annotated.png -- "What the agent read" tab: "No passages yet"
Open the text file ↗
Why this result

The genuinely unreadable file went through Denser’s normal upload path. Marking it ready reported success where a failure notice was required; Denser used a failure status for the password-protected PDF in the same upload.

Tested by Vivek Tomar · evidence dated 17 November 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
Denser AI
Build or version
Not exposed by the hosted product
Plan or tier
Free
Surface
Web app
Set up before the run
A genuinely unreadable truncated PDF had to be uploaded through the dashboard and its ingestion status read. The upload was repeated on 17 November 2026 alongside a password-protected PDF, following an attempt on 5 October 2026.
Tested
17 November 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 →
ToolDenser AI →

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
18 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/denser-ai/a-bad-file-in-the-upload · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-17

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.

Input · Document (PDF) ↗application/pdf · 88 KB
Proof 1 · Screenshot ↗image/png · 171 KB
Proof 2 · Screenshot ↗image/png · 95 KB
Proof 3 · Screenshot ↗image/png · 91 KB
Proof 4 · Captured file (text) ↗text/plain; charset=utf-8 · 3 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)4fee7c30b245797db4b5292c3b0683f218f255fbca0f46abdff0773e65746f58
Proof 1 · Screenshote261212190e2699a2584d834423668e9107e301740ee70937af215dfc2cf11e2
Proof 2 · Screenshotaf8aa29e8542781f4d05668b41ff1363ef0759bca6b2a7ebc572d9d6e9a5c521
Proof 3 · Screenshotaca9efa51e3589466a124fb025624b85aa6ac3b9f30c798707a98e12336c2aae
Proof 4 · Captured file (text)aa521163d14e8923908bf06bdd4895a38ef9467c5cb2f200bfca8e331b1f8097