I have a few scheduled jobs that run in the background. Some of them update data. Some clean things up. Some call external APIs. They are not very exciting, but when one of them stops running, it can create a surprisingly annoying problem. The worst part is that you often do not notice immediately. The job may have failed yesterday, but you only find out today because some data is missing, a report was not generated, or something looks stale. That is the kind of failure I wanted to make more visible. The problem Cron jobs and scheduled scripts are easy to forget about. They usually do not have a UI. They run somewhere on a server, write logs, and disappear into the background. A job can fail because: an API token expired an environment variable is missing a database connection failed the server restarted the script crashed the job started but never finished the cron entry was changed or removed Logs help, but only if you go and check them. For recurring jobs, I usually want a simpler answer: did it run?…