Tidal HELD status causes jobstream runs to become unlinked and possibly generate false alerts.
search cancel

Tidal HELD status causes jobstream runs to become unlinked and possibly generate false alerts.

book

Article ID: 240990

calendar_today

Updated On:

Products

Automation Analytics & Intelligence

Issue/Introduction

When a Tidal jobstream has a Target job, group, or upstream job go into a HELD status it may cause a second jobstream run that is unlinked from the first run.

Environment

Release : 6.4.2-2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL

Cause

6.4.4 added addtional support for Tidal HELD jobs so that they will no longer create a second jobstream run when a job within a jobstream goes into or out of a HELD status.

Resolution

Defect DE547043 had been created for this issue and it is now resolved in 6.4.4.

 

6.4.4 can be downloaded from the link below:

https://support.broadcom.com/web/ecx/solutiondetails?aparNo=99111636&os=MULTI-PLATFORM

 

6.4.4 release notes can be found below:

https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA/latest/AAI%20Guides/Content/Release_Notes/Release_Notes_6_4_4.htm

Powered by Wolken Software