Scrape Health Check

Confirm the daily automated scrape actually ran and actually produced new leads, and catch a silent failure fast. The whole pipeline depends on fresh leads landing every morning. If the scrape quietly breaks and nobody notices for a few days, that is lost speed-to-lead on every notice that posted while it was down, and speed-to-lead is worth more than almost anything else in this business.

Every morning, first thing, before building the day's route or calling block. Also any time you have not seen a health notification by the time you start your day.

• Access to the Discord channel (or equivalent notification feed) the scrape posts its pass/fail signal to.
• A rough sense of what a normal day's lead count looks like for the current city/county rotation, so a low number stands out.
• Access to the health log where results get recorded.

• A green Discord signal exists for today with a lead count that looks normal for the current rotation.
• If the signal was red or missing, it was escalated the same day, not left for later.
• Today's result is logged.

• No Discord signal shows up at all. Treat silence the same as a red signal. Do not assume "no news is good news." Check whether the scrape ran and re-run it if it did not.
• Signal is green but the lead count looks unusually low. A technically successful run can still be a problem if a source went quiet or a city got dropped. Flag it even though the pass/fail signal came back green.
• Signal is red two or more days in a row. This is no longer a one-off blip. Escalate it as a standing issue rather than re-running and moving on, since a repeat failure usually means something upstream needs a real fix.
• Not sure what a "normal" lead count is. Check recent days in the health log rather than guessing, so you are comparing against the actual recent pattern for the current city/county rotation.