Manual forecasts generated for a 24-hour duration in Automic Automation Engine v24․4․1 consistently truncate after 18 to 19 hours․ This behavior is typically observed after upgrading from version 21 and impacts visibility for schedule planning and workload management during high-priority periods․
No specific error message is logged; however, the resulting forecast report stops approximately 5-6 hours early compared to the requested 24-hour window․
SYMPTOMS:
Forecasts initiated from Schedule (JSCH) or Job Plan (JOBP) objects do not cover the full 24-hour period․
Tasks scheduled between 20:00 and 21:00 EST are missing from the forecast output․
Historical data from version 21 confirms these tasks were previously included in 24-hour forecasts․
OS: Windows
Database: MSSQL (Migrated from Oracle)
Automation Engine: v24․4․1 (Build 1750690770737)
Client-side: Automic Web Interface (AWI) v24․4․1
The issue is caused by a time zone calculation mismatch introduced during the upgrade to v24․4․1․ When Schedule or Job Plan objects lack an explicit Time Zone setting, the system defaults to a UTC offset (e․g․, -5 hours for EST), which results in the UI truncating the final 5-6 hours of a 24-hour request as it crosses the UTC day boundary․
Access to the Automic Web Interface (AWI) with administrative permissions. At a minimum, make sure you have permission to modify the Object properties (Schedule/Job Plan)․ We will be explicitly defining the time zone on the Schedule object to ensure the engine calculates the full 24-hour window correctly․
The object now uses the explicit TZ for forecast calculations instead of defaulting to a UTC-based offset that causes truncation․
Verifying Success:
Log out of the AWI and log back in to refresh session metadata․
Navigate to the modified Schedule object and select "Monitoring" -> "Create Forecast" to start from 12AM
Confirm the resulting forecast report shows the full 24 hours of data, including evening tasks․