Tidal jobstreams that have a target job go from a "Completed Abnormally" then has a "Status Change" to "Completed Normally" continue to show as In Progress on the AAI Monitoring tab.

Products

• Automic Automation Intelligence

Issue/Introduction

Tidal jobstreams that have a target job go from a "Completed Abnormally" then has a "Status Change" to "Completed Normally" continue to show as In Progress on the AAI Monitoring tab.

This can cause a false "Exceeded SLA" alert as the jobstream run never completes and will eventually breach the Late Time.

 

For example:

Target job "job_a"

Run 1

Normal Run -> Completed Abnormally (Start time and End Time)

Run 2

Status Change -> Completed Normally (Start time before SLA Time, no End Time)

The jobstream run will still show as running after run 2 even though it is marked as Completed Normally.

 

 

Environment

Release : 6.3.0-2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL

Resolution

Fixed in 6.4.1

https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA/latest/AAI%20Guides/Content/AAI_Topics/Release_Notes_6_4_1/Release_Notes_6_4_1.htm#link9