The way day/date attributes are used has changed. Recall how day/date with time attributes:
Here the day/date act like a guard over the time. Hence the time is not considered until the day/date is free.
task t1 # run on Monday @ 10:00 day monday time 10:00 | task t1 # run on Monday @ 10:00 date 05.08.2019 time 10:00 |
|---|
The definition below in ecflow 4.X.X can produce unexpected run of task t1, on Monday at 00:00
ecflow 4.X
...
family f1
day monday
task t1 # runs Monday@00:00 and Monday@10.00
time 10:00 # time was set free on Sunday
In ecflow 5.X.X the day/date act like a guard over any other time attribute.
Hence the time is not considered until the day is free.
ecflow 5.0
...
family f1
day monday # Guards the time, until day/date is free
task t1
time 10:00 # runs on Monday@10.00
However both behave the same way for the following definition.
...
family f1
time 10:00 # set free on the sunday
task t1
day monday # runs Monday@00:00 and Monday@10.00