...
The behaviour in ecflow 4.0 happens because the time attribute are treated individually. Here the time 10:00, was set free on Sunday. (when time attributes are set free, they stay free, until re-queue.) Code Block |
---|
| ...
family f1
day monday
task t1
time 10:00 # runs Monday an midnight and Monday at 10.00 |
|
---|
Code Block |
---|
|
...
family f1
time 10:00 # time set free on Sunday. Stays free until re-queue
task t1
day monday # runs Monday an midnight and Monday at 10.00 |
In ecflow 5.0, The day acts like a guard over the time.
The time is not set free, until Monday is free.
Hence this produces the expected results.
Code Block |
---|
|
...
family t1
day monday
task t1
time 10:00 # run on Monday @ 10:00 |
Code Block |
---|
|
...
family f1
time 10:00 # time set free on Sunday. Stays free until re-queue
task t1
day monday # runs Monday an midnight and Monday at 10.00 |
Hence in ecflow 5.0, in the following definition, the task will never run:
Code Block |
---|
family f1
day monday
task t1 # t1 will never run, cant be Monday and Tuesday at the same time
day tuesday |
Code Block |
---|