Job status not updated after DB failover

Discussion created by TimothyYanosko604352 on Sep 14, 2017
Latest reply on Sep 14, 2017 by Pete Wirfs
Would like to know if this is working as designed --
We were testing our database fail over process today (AE 11.2/ Windows  agent /SQL 2014) in preparation for our conversion from v9 to 11.2 and came across this scenario. I would like to confirm what was observed is by design. 

Workflow has 3 jobs 

Workflow begins 
Job 1 ends 
Job 2 starts 
AE database goes offline 
Job 2 ends (per agent log) 
AE database comes online 
Job 2 status is not updated, still shows active via GUI 
Workflow and job remain in "active" state via GUI (was later manually cancelled) 
Job 3 never starts. 
Workflow never ends (per GUI)
Sad customers