Statuses
- OK
- The last run reported on time with normal data.
- Running
- The script sent
/startand has not finished yet, within its usual run time. - Late
- The script sent
/startand is taking much longer than usual (or than the expected run time you set). Until a job has 5 measured runs, it turns Late only after one period between its runs (at most 12 hours, never sooner than its grace), unless you set an expected run time. - Missed
- A planned run passed, plus grace, and no ping arrived.
- Failed
- The script reported
/fail, usually with the error message or exit code. - Odd data
- The run finished, but a number broke a rule: rows dropped, a file is empty, a date is stale.
- New
- No ping yet. A new job never counts as missed before its first ping. If it is still New after 3 days (or after twice its period, if that is longer), you get one email about it, only once.
- Paused
- Not watched. After Resume the clock starts again from that moment.
If TaskBeacon itself was unavailable, jobs are not marked Missed for runs in that period; each job continues with its next run. After an outage longer than 3 hours you get an email.
Mark as checked
On a job with a problem, Mark as checked stops the reminders; for odd data it also returns the job to OK.
Use cases: Get an alert when a Stata do-file fails in batch mode · Get an alert when a Python cron job or scheduled script fails · Find out when a scheduled job didn't run at all · Get an alert when a SAS batch job ends with errors · Get an alert when an SPSS Statistics production job fails · Monitor an Excel VBA macro run by Task Scheduler · Monitor a scheduled AI agent or LLM job · Ask Claude or ChatGPT what failed last night · Get an alert when an AI job returns an empty or too-short answer · Get an alert when a job loads 0 rows, or far fewer than usual · Check that a daily table or file is fresh. More questions: FAQ.