2 replies to this topic

[Bill King]

Hi,
I have a Task I am currently testing in the Applications area. This task is currently set to disabled but I am tracking the Launches being generated each day to verify correct scheduling. The task was created on Tuesday, and a launch entry was created for Wed, Thu, Fri, Mon (today), and Tue (for tomorrow following today's execution window) but not for Saturday or Sunday. The rule being used is TV4_J, which is the same rule a task in the Production area is using that has been generating the launches everyday correctly. I have reviewed the rule and everyday is checked off for Worked, Closed, and Holiday. Here is the uxshw RUL:

TYPE | rul

ITEMS | rul : TV4_J
| label : Calendar days
| period : (1d)
| pos : (+1w)
| offset : n
| autho : (yyy,yyy,yyy,yyy,yyy,yyy,yyy)
| authom : (1,2,3,4,5,6,7,8,9,10,11,12)
| authod : +(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,
30,31)
|

I am currently using DU 5.3.3 on a Windows Server environment, and any help you can provide would be greatly appreciated.

-Bill

Attached Files

•  uxshw_FLA.txt   3.22K   3 downloads

[men]

Hi Bill King,

I believe the Rule should be:

period: 1 Day
position: 1 Calendar day from beginning (instead of 1 working day)
offset: no

The masks remain unchanged.

You can either create a new Rule or update the TV4_J Rule and in this case you'll have to select the Task(s) that are using it and choose the "assign Rule" option to update the Rule in the Task. You can then choose the "simulate" option of the Task to check its schedule.

Michel

[Bill King]

Michel,
The position being set as '1 working day' was the culprit and has since been changed. This task in question is "disabled" so a non-execution is a failed execution and the position value goes into effect for the next launch date. My mistake for not seeing that obvious reason. Thanks for the help.
-Bill