Details
-
Fix
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.12, 1.13
-
None
-
None
Description
Current Situation
An order has a run-time like this
<run_time schedule="test"/>
and the schedule test looks like this
<schedule name="test"/>
The next start time is calculated to "never"
The order is executed manually from JOC Cockpit
Looking in the database table SCHEDULER_ORDERS there is then an entry that have in the attribute order.xml this
<order at="2038-01-19 03:14:07.000Z"
what means never.
When now a schedule is created like this
<schedule valid_from="2020-04-03 00:00:00" valid_to="2020-04-07 00:00:00" substitute="test" name="schedule2"> <weekdays > <day day="1 2 3 4 5 6 7"> <period single_start="14:00"/> </day> </weekdays> </schedule>
the run-time of the order is recalculatet to 14:00. The entry in the database is unchanged. When the JobScheduler is restarted in this situation, the run-time for the order is calculated to "never" what is wrong.
Desired Behavior
After restarting JobScheduler all run-times should be calculated correctly.