Yes, I thought about the C1 workflow remembering state after shutdown. For now I rely upon the table cell [jobschedtime] which can be set as a hard dateTime during job creation for either singular or repeatable job scheduling as well as being updated after each iteration. Once I have more time I will get it working with C1 workflow too.
(The underlying concept with this scheduler is that the couple of worker threads are not ultimately responsible for keeping the time of any specific 'job scheduled'. They do a regular loop and check the schedule table if any real jobs need carrying out - if so, then the worker does the heavy lifting and carries out the job or list of jobs it finds (which match what the Worker is configured to handle) in the scheduler table. As C1 reboots, the worker threads start checking the state of jobs in the schedule table, proactively ready instantly to handle a mix of jobs that do not have the "completed" state.
Thanks for mentioning the prospect of turning this scheduler into a C1 package. I think thats a good idea as the design framework is really flexible and would certainly help a lot of folks. After Christmas I will have the time to package up a solid Scheduler integrated fully into C1.
What do you think to the following C1 package concept?
1) Scheduler Framework package.
2) A range of configurable Worker Module packages that can be plugged in to the scheduler.
(The underlying concept with this scheduler is that the couple of worker threads are not ultimately responsible for keeping the time of any specific 'job scheduled'. They do a regular loop and check the schedule table if any real jobs need carrying out - if so, then the worker does the heavy lifting and carries out the job or list of jobs it finds (which match what the Worker is configured to handle) in the scheduler table. As C1 reboots, the worker threads start checking the state of jobs in the schedule table, proactively ready instantly to handle a mix of jobs that do not have the "completed" state.
Thanks for mentioning the prospect of turning this scheduler into a C1 package. I think thats a good idea as the design framework is really flexible and would certainly help a lot of folks. After Christmas I will have the time to package up a solid Scheduler integrated fully into C1.
What do you think to the following C1 package concept?
1) Scheduler Framework package.
2) A range of configurable Worker Module packages that can be plugged in to the scheduler.