Does Anomaly AI respond to a correction made later in a conversation?
Anomaly AI used the customer's correction in its answer. After reporting 18 orders for July 2026, it answered with 11 for June and updated the insight to the corrected period.
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 · Original July question: “How many orders did we get in July 2026?”
Input 2 · June correction: “Sorry, I meant June 2026.”
July answer
You received 18 orders in July 2026, including orders later cancelled. This uses Asia/Calcutta local dates and data last synced October 30, 2026.
Answer after the June correction
You received 11 orders in June 2026, including orders later cancelled. I've updated the insight to June, using Asia/Calcutta local dates and data last synced October 30, 2026.
Transcribed from Proof 1 · Screen recording at 0:25
Every message the tool sent, in order (12)
- Getting tables
Getting tables...
- Calculations resolved
Calculations resolved
- Getting the orders table
Getting table: orders
- Calculation looked up
Calculation looked up
- July data retrieved
Data retrieved
- Query for July orders · not part of the answer
SELECT COUNT(DISTINCT o."id") AS "value" FROM "orders" o WHERE o."placed_at" AT TIME ZONE 'Asia/Calcutta' >= TIMESTAMP '2026-07-01' AND o."placed_at" AT TIME ZONE 'Asia/Calcutta' < TIMESTAMP '2026-08-01'
- Updating the July insight
Updating insight: Orders received in July 2026
- July answer
Printed above.
- June data retrieved
Data retrieved
- Query for corrected June period · not part of the answer
SELECT COUNT(DISTINCT o."id") AS "value" FROM "orders" o WHERE o."placed_at" AT TIME ZONE 'Asia/Calcutta' >= TIMESTAMP '2026-06-01' AND o."placed_at" AT TIME ZONE 'Asia/Calcutta' < TIMESTAMP '2026-07-01'
- Editing the insight
Editing insight (5 changes)
- Answer after the June correction
The final response, printed above.
| ✓ | Expected: Answer for the corrected period only, without retaining or combining the original period.Found: The first answer gave 18 orders for July 2026; the corrected answer gave 11 for June 2026. Its query covered June alone. |
Both periods had data and different counts. The same conversation shows the corrected answer, a June-only query and the updated insight: the correction replaced the original period rather than combining them.
No clarification needed. After the June correction, the agent did not ask which period was meant and said it had updated the insight.
Counting details in both answers. Both order-count answers specified Calcutta local dates, included cancelled orders and said the data was last synced on October 30, 2026.
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 | Anomaly AI → |
Global scenario definition → · Global capability definition → · Anomaly AI 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.