Specific Provoked tasks are not correctly scheduled if Launch Window too long

Products

• CA Automic Dollar Universe

Issue/Introduction

The Specific Provoked tasks are not correctly scheduled when using the property "From" and a launch window of X hours that are more than 23h59, instead they will be launched right away instead of generating a Launch Window in the future at the desired time.
For example, if the main task is scheduled at 17h30, the second uproc on the session has a specific provoked task with the property "From 03:00" and "During 20h59"
When the main task runs, the second uproc will execute at 17h30 instead of generating a launch wait for the next day at 03h00 as expected.

Environment

Dollar Universe 6.x and 7.x

Cause

By design behavior

Resolution

Workaround:

Reduce the Launch Window of the Specific Provoked task so that it won't overlap with the Main Task's Launch Window.

 

Solution:

After analysis & discussion with Product Management, this behavior is by design.

The Specific provoked task has a launch window too long and overlaps the launch window of the main task.
When executing the second uproc of the session, the current algorithm is checking if the launch window is open or not, which is the case here (from 3:00 AM, for 20:59 hours), that's why the launch is created right away.

Additional Information

If you would like to have this behavior changed, please open a RFE as explained here referencing the Rally case DE123644.