Does Draxlr apply a user's corrected metric definition to later questions?
Draxlr retained the user’s corrected metric definition for both a repeated question and a differently worded one. Both revenue answers were $23,194.52, the same as the reference total.
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 metric definition survives a rephrasingPassEvidence
The revenue definition was saved in Train AI: “Our revenue definition excludes cancelled orders and refunded orders.”
Input 1 · Repeated revenue question: “As of September 2, 2026, what was our total revenue over the last 90 days?”
A new chat was opened.
Input 2 · Rephrased revenue question: “As of September 2, 2026, how much did we earn in total over the last 90 days?”
Answer to the repeated question
As of September 2, 2026, total revenue over the last 90 days was $23,194.52. This excludes cancelled and refunded orders.
Answer to the rephrased question
You earned $23,194.52 in total revenue over the last 90 days as of September 2, 2026. This includes orders through September 2 and excludes cancelled or refunded orders.
Transcribed from Proof 1 · Screen recording at 0:20
Everything the tool returned, in order (4)
- Answer to the repeated question
Printed above.
- SQL behind the repeated-question answer · not part of the answer
SELECT SUM(CAST(total_amount AS NUMERIC)) AS total_revenue FROM public.orders WHERE placed_at >= (DATE '2026-09-02' - INTERVAL '90 days') AND placed_at < (DATE '2026-09-02' + INTERVAL '1 day') AND status::text NOT IN ('cancelled', 'refunded') AND refunded_at IS NULL - Answer to the rephrased question
The final response, printed above.
- SQL behind the rephrased-question answer · not part of the answer
SELECT COALESCE(SUM(total_amount), 0) AS total_revenue FROM public.orders WHERE placed_at >= (DATE '2026-09-02' - INTERVAL '90 days') AND placed_at < (DATE '2026-09-02' + INTERVAL '1 day') AND status::text NOT IN ('cancelled', 'refunded') AND refunded_at IS NULL
| ✓ | Expected: The repeated and reworded questions must use the corrected definition and return the reference total of $23,194.52.Found: Both answers excluded cancelled and refunded orders and returned $23,194.52; the reference total was $23,194.52 across 41 orders. |
Both fresh chats used the taught exclusions without another reminder and returned the $23,194.52 reference total. The reference total is reported without the independent database query being shown; the recording shows Draxlr’s own queries and results.
Longer calculation window. Both revenue queries covered 91 days rather than 90. No orders fell on the extra day, so the total was unaffected; the reference calculation used the same window.
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 | Training → | |
| Scenario | The agent used the wrong definition and the user corrects it → | |
| Tool | Draxlr → |
Global scenario definition → · Global capability definition → · Draxlr 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.