Did this work?
Confirm which recommendations shipped, and see what each one saved.
When a recommendation ships, Single Origin measures the cost of the jobs it covers before and after. The Did this work? tab on the Recommendations page is where you confirm what shipped, so the saving is counted. Confirmed savings move to Optimized in prod.
flowchart LR A[Recommendation] --> B[Applied] B --> C[Measured] C --> D[Confirmed]
How a recommendation gets here
A recommendation lands in Did this work? when:
- someone marks it Applied, Applied (Variant) or Partially Applied; or
- Single Origin sees the change it asked for in your query history (for example a new query shape, a settings change or a plan change) and the cost fell. These show as Applied (Unconfirmed) until a person answers.
Single Origin fills in its best guess from your query history. Most of the time you only need to click Correct.
Confirm a recommendation
Each card shows what Single Origin saw under Changes we saw, with What we saw (the evidence, such as the SQL before and after) and Our reading.
For each change, answer Was this change made because of our recommendation?
| Answer | What happens |
|---|---|
| Yes, as proposed | Moves to Applied and is measured from the date you give. |
| Yes, done differently | Moves to Applied (variant) and is measured from the date you give. Add a note on what differed. |
| Partly | Moves to Partly applied; the saving shows as partial. |
| No, unrelated change | Not measured. One Single Origin flagged as applied goes back to Open; one a person marked applied keeps its status. |
| Not sure | Stays in the list. Its status doesn't change and no saving is counted. |
When Single Origin saw no change, it asks What did you change? (code outside the job such as dbt or a PR, settings, schedule, compute size, or Not done yet) and When did this ship?
If you know what it saved, enter the saving a day and How do you know?: Our bill, Query profile or dbt, Rough estimate or Other. Not sure of the saving? Leave it empty and Single Origin keeps measuring.
For a cluster-key recommendation, Single Origin may later ask Is the cluster key still set? If the key is gone, no saving is counted until it is set again.
When the jobs stopped running
If the jobs a recommendation covers stopped running, the card asks Why did it stop?
- Our fix removed it: the jobs' whole cost before counts as the saving.
- Moved to another job: pick Which job took over its queries? from the suggested jobs, or type a job id. The saving is measured over both.
- Another reason: no saving is counted.
How the saving is measured
The recommendation's detail page has a How we measured section. It compares the covered jobs' cost per day before and after the ship date, and shows the result with a margin.
Measurements are frozen at checkpoints 7, 30 and 90 days after the change. A result reads like Saving seen, No saving seen, Cost went up, Waiting for data, Job stopped running or Needs a look.
Where a recommendation names a table rather than a job, the saving is read from the cost of every query that reads the table, around the ship date.
When the numbers disagree
If the saving you reported and Single Origin's estimate are far apart, the Numbers disagree panel shows Our estimate, Your team's number and the number Measured from cost history, with What we checked and the Most likely cause. You choose which number stands.
Optimized in prod
The Optimized in prod tab shows each confirmed win: Shipped date, Before and After cost, Saving a day, and Where it came from (Our estimate or Your team). The header totals Confirmed savings and the Savings run-rate.
From your AI assistant
Your agent can read the same measurement with recommendation_outcome. See Work with recommendations.
Related
Updated about 8 hours ago