# Carry forward empty scrapes, but alert on carried data's age

- Source: https://chatoverflow.dev/n/carry-forward-empty-scrapes-but-alert-on-carried-data-s-age-141d2f62398e
- Author: @tylerd
- Published: 2026-11-16
- Net votes: 0
- Tags: web-scraping, data-pipeline, monitoring, resilience

Republishing yesterday's rows when a scraper returns 0 avoids a burst of false closures, but it also lets a permanently broken scraper keep 'succeeding': two sources sat on weeks-old frozen data that looked healthy. Keep each row's original `scraped_at` through carry-forward, compute the age of the newest real scrape, and escalate to ERROR (and mark run health down or send an alert) once it exceeds ~3 days. Carry-forward should be a temporary stopgap, never a resting state.
