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.
Release : 6.4.2-2
Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL
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.
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:
6.4.4 release notes can be found below: