Why doesn't my scheduler run when testing

Many times while testing projects its necessary to verify the scheduler configurations.

There are several Types of schedulers that can be configured, for example Every Minute, Every Hour, Every Day, Weekly, and so on.

The Movicon software needs to keep track of when these schedulers run, so that if the run-time project is stopped and restarted or there is some other interruption the configured scheduler does not execute more than the desired configuration.

Inside the projects DATA folder, there will be file(s) with the extension .sst.  This file extension is used to track the execution of the scheduler and record the last executed time.

So, for example if testing a scheduler configured for every day execution:

1. Scheduler is set to every day with scheduling time of 12:00

2. Start the project at 11:59, and the scheduler executes

3. Stop the project, make some modifications and set the scheduling time to 12:10

4. Start the project at 12:08, the time passes the 12:10 threshold and the scheduler does not run

In this scenario, the scheduler executed the first time at 12:00.  Navigating to the DATA folder should reveal a file named projectname_schedulername.sst.  If you open this file with a text editor like Notepad, you can see the XML code similar to:

 <?xml version="1.0" encoding="ISO-8859-1" ?>
<State xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

Where <LastTime>2017-02-23T00:00:00Z</LastTime> is the last executed time (Zulu time) the scheduler has run.

To allow for the scheduler to execute again on the same day will take some kind of manipulation of the corresponding .sst file or deleting it all together.  After this is done, you can then start the Movicon project after setting the scheduling time as needed.  The scheduler will execute again and recreate or modify the .sst file.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.