AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 27 October 2026

Does Draxlr keep a report’s meaning when it is rerun after data changes?

Draxlr refreshed the saved report after three orders were added, keeping the same period. Both the report and the database count for that period moved from 26 to 29 orders.

1 of 1 test case passed

Every test case in this scenario has a result.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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 report re-run after new rowsPassEvidence
What we sent

“Show me the number of orders placed in the last 30 days, as of September 2, 2026.”

What the tool returned

You had 26 orders placed in the last 30 days. This covers the 30-day window ending on September 2, 2026, including all of September 2.

Transcribed from Proof 1 · Screen recording at 0:02

Every message the tool sent, in order (2)
  1. Answer

    The final response, printed above.

  2. Generated SQL · not part of the answer
    SELECT COUNT(*) AS order_count
    FROM public.orders
    WHERE placed_at >= TIMESTAMPTZ '2026-09-02 00:00:00+00' - INTERVAL '30 days'
      AND placed_at < TIMESTAMPTZ '2026-09-02 00:00:00+00' + INTERVAL '1 day'
Expected vs. Found
✓Expected: Refresh to the updated database count of 29 orders while preserving the saved report’s relative period.Found: The saved report changed from 26 to 29 orders; the database count for its unchanged period also changed from 26 to 29.
Supporting proof
Proof 1Screen recording
Screen recording: the initial order count, query details and saved report
Key moments
Open original ↗
Proof 2Screen recording
Screen recording: the refreshed saved report and the original chat’s mismatched counts
Key moments
Open original ↗
Proof 3Screenshot
Terminal screenshot: three added orders and database counts before and after
Open original ↗
Why this result

The saved report refreshed live data without changing its period; its one-day counting error is separate from refresh behaviour. The screenshot counts orders only in Draxlr’s own 31-day window; a strict 30-day reference count is not shown there.

Also observed in this test case

Window is one day too long. The last-30-days report counts 31 days as of 2 September 2026, including 3 August, one day too early. After three orders are added, 26 becomes 29; strict 30-day counts are 24 then 27.

Chat text stays stale. In the original chat, the written answer stays at 26 orders while the result card and visualization show 29.

Old value before refresh. The saved-report page initially displays 26, then shows 29 after fetching fresh data.

Tested by Ayush Ghosh · evidence dated 27 October 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.

Software that produced the output
Draxlr
Build or version
Not exposed by the hosted product
Plan or tier
Premium
Model
gpt-5.5-1
Surface
Web app
Set up before the run
The order report needed to use the last 30 days as of 2 September 2026, then be saved and rerun after orders were added within that period. The database needed to allow additions that changed the correct count.
Tested
27 October 2026 · Ayush Ghosh

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

LevelNameScope
BenchmarkAI Database Agents →28 scenarios · 11 tools
CapabilityReporting →
ScenarioThe report is run again after the data has changed →
ToolDraxlr →

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.

from the publication record
18 November 2026First publishedAI Database Agents v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-database-agents/results/draxlr/relative-date-report · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-27

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.

Proof 3 · Screenshot ↗image/png · 22 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recordingc8136bae38c3bffdbf6647fc8aa5221dda370b581e7d307461d701fe61947934
Proof 2 · Screen recording3d77e02b25762caccbbdbc185a6a95883d214e7f8ee7d7fd1b0befd2f67a2b49
Proof 3 · Screenshot8120a0518e3823727f06449999a76139d5b374a59654c95ac9fdef8b15be599e