New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Same field name. Same type. A completely different number underneath.
What you'll have at the end
A written note flagging which fields changed meaning this quarter, with the exact value or definition that shifted
You need
A count or numeric field with at least a month of daily history you can query directly, and a second, independently computed field over the same data whose ratio to the first one means something, such as a raw event count or a companion total rather than another copy of the same number.
Not covered
Catching a field whose name or type actually changes; that is a schema check's job, and this recipe only covers a field that keeps its exact shape while what it counts quietly moves underneath it.
Leans on
Your loudest data quality alert stopped meaning anything
start there instead if the real problem is an existing alert that fires constantly and gets ignored, not a field whose meaning silently changed with no alert at all.
Draft a data contract that survives a schema change
reach for a contract instead when the fix is catching a field's NAME or TYPE changing before it ships; this recipe only covers a field that keeps its exact shape while its meaning moves.
Trace one field from source to dashboard
use that recipe's lineage mapping instead when the job is listing every downstream table and dashboard a field feeds, not deciding whether the field itself changed.
Checked 26 Aug 2026
Part of the Data Observability cookbook