Multiple Jobstream runs are showing starting the same date and either predicted to finish on different days or actually finish on different days in AAI

Products

• Automic Automation Intelligence

Issue/Introduction

Multiple Jobstream runs are showing starting the same date and either predicted to finish on different days or actually finish on different days  in AAI.

 

 

In some scenarios this is resulting in False Exceeded SLA alerts, which should the predicted end time of the next day or the day after and not the current day.

Environment

Release : 6.4.2-2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL

Resolution

Setting a Maximum Jobstream Run Duration may prevent multiple runs from starting the same day and finishing on different days.

This can work around a scenario where AAI is pulling in the previous day into the prediction for the next day, due to the conditions of the jobs in the jobstream.

 

Maximum Jobstream Run Duration(CA7/TES): There may be jobstreams in which job runs that take place sufficiently long before the running of the Target Job run can be ignored. Including these runs may make for an unnecessarily complicated jobstream. In such cases, runs can be excluded if they occurred early enough by setting this duration parameter. This parameter limits job runs in a jobstream run to those runs within the given time duration preceding the end of a Target Job run.

This can be set on a jobstream level for CA7 and Tidal schedulers.

For Autosys there is a server wide parameter set to 24 hours by default.