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.