Forecast ENDED_INACTIVE due to calendar conditions

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Running a forecast on a schedule that contains objects with calendar conditions will not run on a specified date, but instead returns as ENDED_INACTIVE due to calendar conditions. 

When multiple non-zero clients exist in an environment, for instance, clients 100, 200, and 300, and a calendar is copied between these clients, or even just has the same name as a calendar in another client, and it is used for different objects in each of the clients, an issue can occur if the calendars are not maintained identically. 

The calendar in the highest numbered client, in this example case, 300, will be used for all forecasts run in any of the 3 clients in this example. 

Cause

This is due to a defect and has been fixed as of release 21.0.8. 

Resolution

Release version 21.0.8 or later contains the fix for this defect. 

A problem has been fixed where if a calendar exists in a client with a higher ID, and this calendar has the same event but different definition, then the forecast is calculated incorrectly using the definition from the client with the higher ID.