If you want to verify that scheduled tasks work at a very general level, one way is to plan a heartbeat task that works as often as you want. Set a task for updating the counter, change the timestamp, send an e-mail, turn on the SMS βI'm aliveβ every morning, add an entry to the log - which makes sense. This will not tell you that all your tasks are running, but it will tell you that the server is alive and the system of scheduled tasks is working.
Another option is to complete your tasks with a single entry point - a kind of front controller for tasks. This delegates the setting up and setting up individual tasks for your code, not the CF admin. The main task controller will include a startup code for each task. Plan for the dispatcher to work as often as needed - just one task, not many. In the controller, something like this, maybe every five minutes:
Check the time/date, compare against set of tasks If time (or frequency) is A, run tasks P,Q,R, log success/failure If time is B, run tasks S,T, log success/failure If time is C, run tasks U,V,X, log success/failure Send heartbeat with success/failure codes for all relevant tasks
One of the advantages of this approach is that you can express much richer go / no-go workflows - tasks are performed at semi-randomized frequencies, run tasks based on the success or failure of other tasks, etc. If you see / get a heart rate indicator, you know that your task controller has actually been executed.
source share