Does AskYourDatabase update its answer when a customer corrects earlier information?
AskYourDatabase answered the corrected period only. The July question returned 23 orders, and the follow-up June correction produced a new June query and 10 orders, with the thread ending there.
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 is based on this test case.
Corrected period replaces the originalPassEvidence
Input 1: “How many orders did we get in July 2026?”
Input 2: “Sorry, I meant June 2026.”
Response 1 (July lookup) is a progress message the tool sent for Input 1; it is not part of the answer.
Response 2 (July SQL) is the query the tool generated for Input 1; it is not part of the answer.
Response 3 answers Input 1.
Response 4 (June SQL) is the query the tool generated for Input 2; it is not part of the answer.
Response 5, the final response, answers Input 2.
You received 10 orders in June 2026.
Transcribed from Proof 2 · Screenshot
Every message the tool sent, in order (5)
- July lookup
I'll look up the number of orders placed in July 2026.
- July SQL · not part of the answer
SELECT COUNT(*) AS order_count FROM orders WHERE placed_at >= '2026-07-01' AND placed_at < '2026-08-01'
- July answer
You received 23 orders in July 2026.
- June SQL · not part of the answer
SELECT COUNT(*) AS order_count FROM orders WHERE placed_at >= '2026-06-01' AND placed_at < '2026-07-01'
- June answer
The final response, printed above.
| ✓ | Expected: Only the corrected month should be answered, not the original month or a combined total.Found: The follow-up produced a June-only query and returned 10 orders; the July count and any combined total were not repeated. |
The product took the correction as a new month and returned the June count only. It did not repeat the July count or combine the two months, so the corrected period is what appears.
No intro line. The correction turn goes straight to SQL, unlike the first turn.
No July restatement. The June reply names June, but it does not say it replaces the July answer.
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 | Conversational Interaction → | |
| Scenario | Customer corrects information given earlier → | |
| 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.