Does FutureSmart Database Agent keep a report meaningful when rerun after the data has changed?
FutureSmart Database Agent did not demonstrate that a report rerun after data changes preserved the same relative window. It returned 57 for the preceding 30 days as of September 2, 2026, and the visible answer surface showed no save/report control or refreshed report to compare after new rows were 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 counts this row.
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. COUNT 57
Transcribed from tc55-orders-last-30-days-result-detail
These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the rerun preserves the original question rather than becoming a different report.
- Whether the refreshed result is recomputed against the changed data state.
- Whether the answer still means the same thing as the saved report, not a frozen past result.
| ✗ | Found: No refreshed result is shown; the visible query still returns 57 for the same relative 30-day window. |
The product shows the same relative 30-day query returning 57, but no save or report control is visible. With no saved report shown, a refreshed result after added rows cannot be verified.
Relative window kept in SQL. The SQL keeps the period relative by using the September 2, 2026 anchor minus INTERVAL '30 days' rather than hard-coded dates.
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 | AI Database Agents → | 28 scenarios · 4 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.