Can AskYourDatabase handle a customer correcting an earlier request?
AskYourDatabase handled a customer correction in this conversation. After the July 2026 question returned 23 orders, the follow-up “Sorry, I meant June 2026.” triggered fresh June-only SQL and a June answer of 10.
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.”
The tool's reply is shown in the screenshots under Proofs.
| ✓ | Expected: Use only the corrected period, not the original or both together.Found: The second turn used June only and answered 10. |
The two turns and their SQL were checked. After the July 2026 answer of 23, the correction to June 2026 produced fresh June-only SQL and an answer of 10, replacing the earlier period.
Correction goes straight to June. The second turn goes straight to the June query and answer; it does not introduce the correction before the SQL.
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 · 4 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.