Can Dot save an answer and reopen it later?
Dot kept the answer available for reopening. Saving it as an app and reopening it in a new session showed the same title, date range, and June/July/August values, and the saved app re-ran the same query.
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.
Saved answer reopened in a new sessionPassEvidence
Input 1: “Show me our monthly order count for the last 3 months, as of September 2, 2026.”
Input 2: “customer_support_db”
Input 3: “Save this answer as an app called "Scenario 54 - Monthly order count" so I can open it again later.”
Response 1 answers Input 1.
Response 2 is a progress message the tool sent for Input 2; it is not part of the answer.
Response 3 answers Input 2.
Response 4, the final response, answers Input 3.
Saved as “Scenario 54 - Monthly order count,” with June–August 2026 as the default date range.
Transcribed from Proof 1 · Screen recording at 1:48
Every message the tool sent, in order (4)
- Response to input 1
Which order dataset should I use: customer_support_db or order_status? And should “last 3 months” mean June–August (complete months), or July–September 2 (September partial)?
- Progress message for input 2
Analyzing your question
- Response to input 2 (message 2 of 2)
Monthly orders were 11 in June, 18 in July, and 28 in August
- Final response
Saved as “Scenario 54 - Monthly order count,” with June–August 2026 as the default date range.
| ✓ | Expected: Reopening should show the same answer and make clear it is the same question.Found: The reopened app matches the original answer’s title, date range, and June/July/August values, so it is the same question. |
It is a pass, not a fail, because reopening shows the same saved answer with the same title, date range, and June/July/August values in a new session.
Saved app re-runs. The saved app came back with the same three values, and it behaves like a live app that re-runs the pinned query instead of replaying a frozen transcript.
Clarifying first. Dot asked which dataset to use and what the date window should mean before giving the answer; the customer then supplied customer_support_db.
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 user wants to keep an answer they just got → | |
| Tool | Dot → |
Global scenario definition → · Global capability definition → · Dot 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.