Does AskYourDatabase preserve a report’s relative period when it is rerun after data changes?
AskYourDatabase answered the relative-period order question, but no save control was found for rerunning the answer as a report after data changed. The answer actions offered copying and PDF printing.
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.”
21 orders were placed in the 30 days leading up to September 2, 2026 (i.e., between August 3 and September 2, 2026), excluding cancelled orders.
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (3)
- Query progress
I'll query the database for orders placed in the last 30 days as of September 2, 2026.
- Generated SQL · not part of the answer
SELECT COUNT(*) AS order_count FROM orders WHERE status != 'cancelled' AND placed_at >= '2026-09-02'::timestamp - INTERVAL '30 days' AND placed_at < '2026-09-02'::timestamp
- Answer
The final response, printed above.
| ✗ | Expected: After rows are added, rerun the saved report using the same relative period and return the updated correct answer.Found: No save or report control was found beneath the answer or across the bot, dashboard, data-source, billing, API-key and general settings pages. |
The required refresh needed a saved answer. The question received an answer, so missing report-saving capability—not an execution fault—prevented progress. PDF printing is static, and the dashboard builder uses a database structure and description rather than saving chat answers.
End-date wording. The order-count answer names September 2, 2026 as the end date; its query excludes that date, making the stated end date one day later than the query’s.
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 | AskYourDatabase → |
Global scenario definition → · Global capability definition → · AskYourDatabase 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.