Forecast for Schedule JSCH Objects is wrong when Timezone is used
search cancel

Forecast for Schedule JSCH Objects is wrong when Timezone is used


Article ID: 190559


Updated On:


CA Automic One Automation


Timezone is ignored when using forecast for schedule object
Forecast and Autoforecast shows in GMT time only

Steps to reproduce:
1. Create schedule object, define period turnaround at 00:00 and time zone, for example CET
2. Schedule some object there, for example to start at 00:00:
3. Then create forecast, for example for tomorrow 08.10.2019 and use start time 00:00 as at this time schedule is turnaround:
4. In forecast you can see that forecasted script has finished with status start time exceeded. And you can see that schedule logical start is at 00:00 and estimated time at 02:00, so it seems that system used UTC or GMT time to calculate times even though the schedule has a different time zone set


Release :  12.3 and 21



This is caused by a defect in the Automation Engine component that calculates forecasts, several correction attempts had to be made on different versions to completely fix the problem.



Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine 

Automation.Engine 12.3.9  - Available
Automation.Engine 21.0.4 - Available

Additional Information


Use the Timezone object inside of the Schedule object, that will allow Autoforecast properly calculate the time.

Solution details:

A bug has been fixed where forecasting schedule objects (JSCH) did not deliver expected results. Now they do, even if the objects do not have time zones set.