Forecast “Estimated Run Time” is not utilizing the, “Use fixed value,” definition that was selected - it is using the actual runtime. This is an issue when attempting to create a forecast on new jobs that have never ran. In addition, associated calendar time zones are being considered, but they are being reported in the time zone of the Automation Engine - not the time zone defined for the jobs.
!) Create a job.
2) Configure the job to utilize TZ.SYD.
3) Create a Workflow.
4) Configure it to utilize TZ.WA.
5) Place the job in the workflow, and set the job's earliest start time to 8:09am.
6) Save the workflow.
7) Right click on the workflow from the Web Interface (AWI).
8) Select Create Forecast.
9) Set the logical start data in the future (for this example, 7/7 was utilized).
10) Use a fixed value of 10 minutes.
11) Run the Forecast.
*The logical start shows 7/7 at 12:57, which isn't correct (Sydney time is 18 hours ahead of Pacific, so this should be roughly 2:00am 7/8).
*In addition, the estimated end is only 1 minute (not 10, as specified via USE FIXED VALUE when creating the forecast) for the job and workflow which have never been executed before.
This forecast behavior has been identified as incorrect.
The fix for this issue is slated for release with the following Automation Engine components and versions:
Automation Engine 12.1.3, Planned Release 9/24/2018
Automation Engine 12.2.1, Planned Release 10/23/2018
Automation Engine 12.3.0, Planned Release 2/28/2019