Does FutureSmart Database Agent keep a report meaningful when rerun after the data has changed?
FutureSmart Database Agent failed this scenario. The pinned question returned 57 for the 30-day window, but the console sweep shows no way to save an answer as a report or rerun one, so the result cannot refresh after rows are added.
1 of 1 test case failed
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 is based on this test case.
Saved report re-run after new rowsFailEvidence
“Show me the number of orders placed in the last 30 days, as of September 2, 2026.”
Orders Placed in the Last 30 Days As of September 2, 2026, the total number of orders placed in the preceding 30-day period is 57.
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (2)
- Final response
The final response, printed above.
- Generated query · not part of the answer
SELECT COUNT(*) FROM orders WHERE placed_at ≥ TIMESTAMP '2026-09-02 00:00:00+00' - INTERVAL '30 days' AND placed_at ≤ TIMESTAMP '2026-09-02 23:59:59+00'
| ✗ | Expected: A saved report rerun after rows are added should show the new count for the same relative period.Found: It returned 57 for the pinned run, and the console shows no way to save or rerun a report. |
It fails because the case required a saved report to rerun after matching rows were added, and the console shows no save-as-report or rerun control anywhere, so the refreshed result cannot appear.
No refresh path. With no saved report, added rows had nothing to refresh.
The later steps were never reached, so there is no saved report or rerun output.
The evidence does not show which plan the account was on, and the sweep recordings show no locked control or upgrade prompt.
The sweep recordings were captured on 21 October 2026, about six weeks after the run, so they show the console then, not on the run date.
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 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Reporting → | |
| Scenario | The report is run again after the data has changed → | |
| Tool | FutureSmart Database Agent → |
Global scenario definition → · Global capability definition → · FutureSmart Database Agent product page →
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.