TSCron | TSCron ... a Google Form based Cron scheduler

Login to Google Drive. Access the TSCron form. Click the Use Template button. This will copy the form to Google Drive. Locate and open the newly copied TSCron form and add any optional user defined form elements needed to implement the cronJob() function. Be sure to add these optional form elements to form section(s) BEFORE the pre-existing TSCron configuration form elements. Any form submission responses for user defined form elements will be passed to the cronJob() function as an array of ItemResponses each time the cron job executes. Be sure to set the Continue to next section option on the TSCron form section preceding the pre-existing TSCron configuration section. Open the TSCron form's script editor. Implement the cronJob() function in the supplied Code.gs file using Google Apps Script. This file can be found within the TSCron form's Script Editor.
Login to Google Drive.
Access the TSCron form.
Click the Use Template button. This will copy the form to Google Drive.
Do not add, delete or modify any form element or form section ON OR AFTER the pre-existing TSCron configuration form elements or the cron scheduler will cease to function properly.
Do not add any user defined elements with the title Run TSCron.
e - time-driven event object which contains information for the current cron execution (see 'time-driven events' in the Google Apps Script documentation for more information). The event object is represented in Coordinated Universal Time (UTC).
params - an array of any user defined ItemResponses for the form elements defined in Step #2 (NOTE: If no user defined form elements exist this parameter will be null)
Test for a null value in the passed params function parameter
Use the Lock Service to prevent any concurrent access to sections of code within the cronJob() function which might modify a shared resource. This is particularly important when implementing longer running processes on a short Minutes cron interval where multiple cronJob() executions could occur simultaneously.
Wrap the cronJob() implementation code in a try/catch block and send an email on any error conditions
Do not create a "Script" PropertiesService value with the key tscron or the cron scheduler will cease to function properly.
Do not create any form submit triggers using the existing TSCron function newTSCron or the cron scheduler will cease to function properly.
Do not create any time-based triggers using the existing TSCron functions startTSCron, runTSCron or endTScron or the cron scheduler will cease to function properly.
Be sure to run the Configure option BEFORE submitting to the form or the cron scheduler will not work.
If code requiring additional user authorization is added to the cronJob() function, the authorization process must be repeated for TSCron to continue to operate correctly. Re-run the Configure menu option to re-authorize.
When scheduling a new cron the start date/time must be at least 15+ minutes in the future of the form submission and the optional end date/time must be scheduled at least 1 hour after the start date/time. NOTE: The cron job will not be scheduled and an error message email will be sent to the form owner if these conditions are not met.
Actual cron execution times may vary +/- 15 minutes from the original schedule dates/times.
If a failure occurs during the initial or subsequent cron scheduling, TSCron will be disabled and an error message email will be sent to the form owner. Restart the cron job by submitting another form request.
Cron scheduling uses the Google Form owner's default time zone (determined by the form's associated Google Apps Script project properties - see File -> Project properties -> Time zone in the form's Script Editor).
If the TSCron default time zone is modified to a new time zone the cron schedule will remain on the previous time zone. You must submit a new response to the form to get an updated cron schedule in the new time zone.
Do not delete form responses while there is a running cron job or the cron scheduler will cease to function properly.
Do not delete any TSCron related triggers from the form while there is a running cron job or the cron scheduler will cease to function properly.
Because cron schedule times can vary +/- 15 minutes, the cron job could potentially execute after the original end date/time but before the cron job is stopped.