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
A pipeline finished green three days ago, and nobody noticed the source stopped sending new rows until the numbers looked flat.
What you'll have at the end
A script that checks one table's last-updated time and row count against yesterday's, and fails loudly when either one is off.
You need
A table a scheduled job loads on a regular daily cadence, with a column recording when each row's real event happened, and a query that can count how many rows landed for a single day's load rather than the table's whole history.
Not covered
Checking whether a value inside a row that did land is actually correct, such as a wrong total or a renamed column; this only watches whether new rows showed up on time and in a normal amount.
Give every load a data quality gate
once new rows are arriving on time and in a normal amount, that's the check for whether the values inside them are actually correct
Catch schema drift early
a table can look fresh and full while a source quietly renamed or retyped a column underneath it; that needs a different check entirely
Checked 25 Aug 2026
Part of the Big Data cookbook