Schedules
A schedule tells TaskBeacon when a run is expected, so it can tell you when one is missing.
Daily, weekly, monthly or every N minutes
- Daily: every day (or every N days) at a time.
- Weekly: on the weekdays you tick, at a time; optionally every N weeks.
- Monthly: on the days of the month you tick; Last is the last day of each month.
- Every … (minutes, hours or days): counted from the last ping, for jobs without a fixed time.
- Repeat job every … for a duration of …: for jobs that run, say, every hour during working hours.
The editor shows the next five planned runs as you change it.
Grace
Grace is the extra time a run may take to report before it counts as Missed. Too tight gives false alarms; too loose and you hear late. After a few runs TaskBeacon suggests a grace that would have covered your real runs (test pings in the first hour after you made the job are left out). Expected run and Late after are under Advanced timing on the Edit page: leave them as they are and TaskBeacon learns the usual run time.
Time zone
Schedules use your time zone from Settings → Account. Days in no-alert days have no planned runs at all.
Use cases: Task Scheduler can't send email any more: get an alert when a task fails · Know when a scheduled R script fails · Find out when a scheduled job didn't run at all · Heartbeat monitoring (a dead man's switch) for scheduled scripts · SQL Server Agent job failure alerts without Database Mail · Monitor an Excel VBA macro run by Task Scheduler · dbt Cloud job failure alerts, and runs that never started. More questions: FAQ.