Releases that move your findings

The counts on the home page were already links, and all of them opened the same unfiltered page. That is the first half of the answer and it reads as the whole of it: “6 health findings” took you somewhere that might show five, because the list opens on what is outstanding while the count includes what you have already acknowledged.

Each one now carries its own filter. Failures opens the things that stopped running. Health findings opens the open and the acknowledged together, which is what the number adds up. Saved per month opens the resolved findings the money was worked out from — it used to open the ones still outstanding, which is the opposite set, so checking a saving showed you the work still to do.

When Gecko investigates a failure and is genuinely torn between two explanations, it can now record both — the one it chose and the ones it did not, each with the reason it was ruled out. They appear under the root cause as “Also considered”. Most diagnoses still have one cause and show nothing extra; this exists for the case where presenting a single answer would claim more confidence than there was.

When an investigation ends without an answer, the message now says where Gecko looked — how many files it read, which models it walked, how many queries it ran. That comes from what the run actually did, not from the agent’s account of its own effort.

A column whose type narrowed — VARCHAR(255) to VARCHAR(10), NUMBER(10,4) to NUMBER(10,2) — is now counted as a breaking change and named apart from one that widened. Both were reported as “type changed”, which treats a schema as a set of names rather than of shapes: widening costs nobody anything, narrowing is a loss of data waiting for the row that triggers it.

Projects with two source-control connections can now say which repository holds the dbt project, instead of Gecko choosing the one edited most recently.