>suddenly, silently, stops working Not to detract from your overall point but for anyone out there wondering about a way to handle this in general: your job sh

>suddenly, silently, stops working Not to detract from your overall point but for anyone out there wondering about a way to handle this in general: your job should update or annotate something (a file, a table, a bucket, etc.) upon success. Then you use a "dead man's switch"-style check/monitor that alerts if the job hasn't updated its proof of life, so to speak.