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

Can Vectara report a bad file during upload?

Vectara reported files it could not process during upload. It returned errors for a truncated PDF and a password-protected PDF; the console also showed the truncated file's failure.

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.

Unprocessable file submitted through the normal upload pathPassEvidence
What we sent

We submitted a truncated PDF and a password-protected PDF through the upload API.

What the tool returned

API response

HTTP 400 { "field_errors": { "body.file": "File could not be parsed. It may be a corrupt archive or a malformed document." }, "request_id": "df999873-18a6-4dbf-a846-eb7f0b14c538" }

API response

HTTP 400 { "field_errors": { "body.file": "File is encrypted. Remove password before indexing." }, "request_id": "5fa477e8-14b0-4746-ad73-059bd6c012d9" }

Transcribed from Proof 3 · Screenshot

Everything the tool returned, in order (3)
  1. API response

    Printed above.

  2. Upload-status table row

    bad_01_truncated.pdf | Error: 400 | Failed to parse PDF: Could not find trailer entry while repairing ()

  3. API response

    The final response, printed above.

Expected vs. Found
✓Expected: A failure is reported for the affected document.Found: The truncated PDF received HTTP 400 and a console error, with nothing indexed for it. The password-protected PDF also received HTTP 400 with a file-specific reason.
Supporting proof
Proof 1Screenshot
Notebook screenshot: API upload and response for the truncated PDF
Open original ↗
Proof 2Screenshot
Console screenshot: upload status for the truncated PDF
Open original ↗
Proof 3Screenshot
Notebook screenshot: API upload and response for the password-protected PDF
Open original ↗
Proof 4Captured file (text)
Evidence summary: repeated truncated-file responses, console status and password-protected file response
Text50 lines
TC89 — Vectara — R6 Managed RAG v1
Operation: submit a genuinely unprocessable file through the normal upload path, read the ingestion status.
File: bad_01_truncated.pdf (truncated PDF, no trailer — genuinely unparseable, not merely unusual)
Endpoint: POST /v2/corpora/r6-managed-rag-ss-v1/upload_file

====================================================================================================
API response (4 identical requests, same file — showing message non-determinism)
====================================================================================================

Attempt 1: HTTP 400
{"field_errors": {"body.file": "File could not be parsed. It may be a corrupt archive or a malformed document."}, "request_id": "df999873-18a6-4dbf-a846-eb7f0b14c538"}

Attempt 2: HTTP 400
{"field_errors": {"body.file": "Failed to parse PDF: Could not find trailer entry while repairing ()"}, "request_id": "0f2b02ef-014e-4274-acb1-fe9f1df00db9"}

Attempt 3: HTTP 400
{"field_errors": {"body.file": "Failed to parse PDF: Could not find trailer entry while repairing ()"}, "request_id": "19a35069-94c5-4dea-830f-c08e396ba04e"}

Attempt 4: HTTP 400
{"field_errors": {"body.file": "File could not be parsed. It may be a corrupt archive or a malformed document."}, "request_id": "8f02fe64-33f0-4c83-b1e4-f4beda66cddf"}

All 4 attempts: HTTP 400, non-empty field_errors.body.file. Never a silent success, never HTTP 200/201.
Wording varies (2 distinct messages observed) but the failure signal itself is 100% consistent.

====================================================================================================
Console UI response (same file, uploaded via the "Upload files" screen)
====================================================================================================

Uploaded 0 files with 1 error

File name: bad_01_truncated.pdf
Status: Error: 400
        Failed to parse PDF: Could not find trailer entry while repairing ()

The UI surfaces the same failure signal live, per-file, in the upload-status table — not just the
API response. Screenshot: tc89-vectara-console-upload-error.png

====================================================================================================
Alternate bad file — password-protected PDF (generated: A01 re-saved with pypdf, user password set,
not present in the original fixture set)
====================================================================================================

POST /v2/corpora/r6-managed-rag-ss-v1/upload_file with bad_02_password_protected.pdf:

HTTP 400
{"field_errors": {"body.file": "File is encrypted. Remove password before indexing."}, "request_id": "5fa477e8-14b0-4746-ad73-059bd6c012d9"}

Even more specific than the truncated-file case: correctly diagnoses the exact problem
(encryption) and tells the user exactly what to do about it. Second independent confirmation that
Vectara reports per-document ingestion failures rather than claiming success or staying silent.
Open the text file ↗
Why this result

The requirement was to report a failure for the affected document. Both genuinely unprocessable files received document-specific failures rather than success or silence.

Also observed in this test case

Error wording varied. Across four identical uploads of the truncated PDF, the API alternated between a general parsing error and a specific missing-trailer message. Each returned HTTP 400 with a reason.

Password guidance. For the password-protected PDF, the API identified encryption and said to remove the password before indexing.

Tested by Vivek Tomar · evidence dated 10 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
Vectara
Build or version
v2
Surface
API
Set up before the run
The test required a file that genuinely could not be processed, rather than one that was merely unusual. It was to be submitted through the normal upload path, with the product's ingestion status read afterward.
Metadata region
UK
Tested
10 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
CapabilityData Ingestion →
ScenarioA bad file in the upload →
ToolVectara →

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

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 · 135 KB
Proof 2 · Screenshot ↗image/png · 72 KB
Proof 3 · Screenshot ↗image/png · 145 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.

Proof 1 · Screenshot53b45d1de8ef6257815e26d34cfc34476f8e23f3666b3732035b7ca15334a8e6
Proof 2 · Screenshot0f4f2a6d7d99568ab01a783db170d38b6702667f33cc9f47423e970c894cb132
Proof 3 · Screenshote1d67f718cbf717b7db4a6517e8389ab6bac4f2f0709c02b09da519eaba16a54
Proof 4 · Captured file (text)93962bafc5ef005166a8ce359d5e0e08511eaf92919bfc76a164bbd583d8cc4c