Scheduling mechanism for CoolAutomation's Cloud apps
This article applies to the following CoolAutomation products:
The iocControl & Professional App schedules have a "schedule verification" process:
2 minutes after a schedule is executed, a validation check that the scheduling has been completed successfully is initiated.
If the validation process results indicate that the schedule wasn't successful, the scheduled task will be executed again.
Once again, 2 minutes after we have rerun the schedule, a second validation check is done. if the results of the validation process indicate that again there is a failure, an alert will be logged into the app.
Note that a scheduled task is considered to be successful only if all of the defined actions in the scheduled task were performed successfully. If only partial success is identified, then the above process will be executed.
As an example:
A schedule to turn off the AC units at 19:00 is configured in the App.
At 19:00 the schedule is triggered and a command to turn off the AC units is sent.
At 19:02 a validation process is triggered, checking that the AC units were turned off.
If the AC units were not turned off, the schedule will run again and try to turn off the AC units.
At 19:04 a second validation check is done to see if triggering the second schedule cycle was successful and the AC units are turned off.
If the AC units were not turned off, an alert will be logged in the APP