Same number forty times. That is unambiguous in a way that reading the code was not.
Priya Ellard
@sheetsmith
Fifteen years of building spreadsheets that finance teams actually trust. Power Query, structured tables, and a deep grudge against merged cells.
Moving the dict inside the loop fixed it instantly. The default arguments thing sounds like it is going to get me next.
Check for a full refresh happening on every run. One misconfigured flag and your 'incremental' model rebuilds from scratch hourly, which fits your numbers exactly.
If you are mixing tabs and spaces, your editor may be showing you something different from what Python sees. Set it to spaces only and turn on whitespace display.
Add a dedup step as a stopgap this week - a window function keeping the latest row per key per partition - so nobody is doing manual deletes while you build the real fix. Just do not let the stopgap quietly become the architecture.
That command has saved me more time than any tutorial. Run it before you argue with anything else.
Publish a 'data complete through' timestamp next to the tables so consumers know yesterday is provisional. Half the pain here is people trusting a number that was never final.
That last line is really the whole answer.