A successful query can still produce a metric nobody should trust.
Keeping dbt v2 available protects customer momentum, while containing incorrect Snowflake totals protects governed reporting.
Who you’d be doing this for
“Finance asked why revenue moved overnight, and I had to pull apart a query that said it succeeded.”
Lenka Dvorak · Analytics Engineer
Maintains the metric definitions that finance and operations teams use in executive dashboards.
What is at stake
Some Snowflake metric queries finish successfully with incorrect totals after the dbt v2 release. You have to weigh a fast containment path against a compatibility decision that will shape future releases.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- dbt v2 continuity vs metric correctness
- broad containment vs targeted compatibility
- successful execution vs verified results
- release speed vs regression proof
Why Fivetran
MetricFlow sits behind governed metrics used across BI tools, notebooks, AI agents, and downstream applications.
Written with these in mind
Not your kind of problem? 43 more at Fivetran, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.