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.
Target job "job_a"
Normal Run -> Completed Abnormally (Start time and End Time)
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.
Release : 6.3.0-2
Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL
Fixed in 6.4.1