"A script that never starts can't report its own absence" sums up the problem nicely. Plain HTTP pings with an expected interval and grace period keep it easy to add to existing cron jobs, and flapping suppression should save a lot of noisy alerts.
PulseWatch reviews
What 2 Uneed members think of PulseWatch
Are solo devs mostly adding PulseWatch to nightly database backups first, or to scraper and sync scripts that tend to hang rather than fail outright? Happy to record a free feedback video where I set up a first monitor as a new user and call out anything unclear.
Hey! Appreciate the question. There is some of that nightly backup stuff going on. Also there’s the script hangs that we can catch. So, a bit of both I guess.
foundernotesOct 18, 2026
Makes sense, the hangs are the sneaky ones since nothing errors out, the job just quietly never finishes. Do people usually set the expected runtime themselves, or does PulseWatch learn what normal looks like for each script? Still happy to record a free feedback video where I set up a first monitor as a new user and point out anything confusing, if that would help.