Forecast ignores the Earliest Start Time of the Start of a Workflow
search cancel

Forecast ignores the Earliest Start Time of the Start of a Workflow

book

Article ID: 366705

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The output of the forecast feature has changed.
In version 12.2.3 the logical start time of the Jobs showed the Earliest Start time of the underlying tasks.
In version 21.0.8 this is no longer the case it shows the same time as the logical start time of the workflow.

Scenario to use for the tests to reproduce the problem:

Actual Results
  • The Workflow is waiting for the start time (OK), but the Forecast says it is running immediately (NOK).
Expected Results
  • The Forecast should consider that Earliest Start Time

Reproducing scenario

1.) Create a Workflow, with a task. Define earliest start time under the Start object's properties -> Time and Dependencies tab. (e.g. 8:00 PM)
2.) Create a schedule object and put the workflow object above in it with a start time configured earlier than the above configured (e.g. 11:00 AM)
3.) Create a Forecast via right clicking the schedule object above -> Monitoring -> Create Forecast with a Logical Start time earlier than the above (e.g. 10:00 AM)
4.) Open the forecast.

Environment

Automation Engine 21

Cause

This is a defect in the Automation Engine 

Resolution

This bug will be fixed in a near version.

Additional Information

Bug ID: AE-31105
Bug Tile: Forecast ignores the Earliest Start Time of the Start of a Workflow.