Does FutureSmart Document Intelligence report when an upload cannot be processed?
FutureSmart Document Intelligence passed this upload scenario: it reported both bad PDFs as failures instead of ingesting them. The truncated file and the password-protected file were both rejected; the app said each could not be uploaded, and the API returned HTTP 500.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above counts this row.
Unprocessable file submitted through the normal upload pathPassEvidence
status: 500 / { "type": "https://developers.futuresmart.ai/document-intelligence/errors#internal_error", "title": "Something went wrong on our side", "status": 500, "code": "internal_error", "request_id": "req_dadb971cb3f840d5b015" } status: 500 / { "type": "https://developers.futuresmart.ai/document-intelligence/errors#internal_error", "title": "Something went wrong on our side", "status": 500, "code": "internal_error", "request_id": "req_570620ff24574742b66d" } 1 file could not be uploaded: bad_01_truncated.pdf (Error checking PDF page count: 400: Could not process the PDF from the URL. Details: 400: Could not process the provided PDF file. It may be corrupt.) Dismiss 1 file could not be uploaded: bad_02_password_protected.pdf (Error checking PDF page count: 400: Could not process the PDF from the URL. Details: 400: Could not process the provided PDF file. It may be corrupt.) Dismiss
Transcribed from Proof 3 · Screenshot
Transcribed from Proof 4 · Screenshot
Transcribed from Proof 1 · Screenshot
Transcribed from Proof 2 · Screenshot
Every message the tool sent, in order (4)
- Final response (message 1 of 4)
status: 500 / { "type": "https://developers.futuresmart.ai/document-intelligence/errors#internal_error", "title": "Something went wrong on our side", "status": 500, "code": "internal_error", "request_id": "req_dadb971cb3f840d5b015" }
- Final response (message 2 of 4)
status: 500 / { "type": "https://developers.futuresmart.ai/document-intelligence/errors#internal_error", "title": "Something went wrong on our side", "status": 500, "code": "internal_error", "request_id": "req_570620ff24574742b66d" }
- Final response (message 3 of 4)
1 file could not be uploaded: bad_01_truncated.pdf (Error checking PDF page count: 400: Could not process the PDF from the URL. Details: 400: Could not process the provided PDF file. It may be corrupt.) Dismiss
- Final response (message 4 of 4)
1 file could not be uploaded: bad_02_password_protected.pdf (Error checking PDF page count: 400: Could not process the PDF from the URL. Details: 400: Could not process the provided PDF file. It may be corrupt.) Dismiss
| ✓ | Expected: The file's failure had to be reported; success or silence would fail.Found: Both bad PDFs were rejected: the app showed a failure banner and zero documents, and the API returned HTTP 500. |
The case required an unprocessable file to be reported as a failure. Both bad PDFs were unreadable, and each upload produced a failure message or a 500 response, so the product reported the problem instead of acting as if ingestion succeeded.
API error detail. The API returned only a generic internal error, while the app screen showed the more specific processing message.
No document row. Rejected files never became document rows; the page stayed at Failed 0 and reported the problem at upload.
The two attached PDFs are the test files, but the page does not show they are byte for byte the uploaded files.
Only the truncated and password-protected files were tested; the not-a-PDF case was not run.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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 row says which 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 row 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Managed RAG → | 15 scenarios · 8 tools |
| Capability | Data Ingestion → | |
| Scenario | A bad file in the upload → | |
| Tool | FutureSmart Document Intelligence → |
Global scenario definition → · Global capability definition →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.