Job :rops.MSM2_edwtuc_p_c_a2b_file_watcher_CONS in PG2 is changing status automatically (without any manual intervention) to SUCCESS when kept ON_HOLD .
Please look into this issue and let us know what might be causing this issue.
Job was ON_HOLD all this while and it was force started by application team 2-3 days back and was made active, but now if they put job back ON_HOLD, as told it is changing status to SUCESS and upcoming scheduled runs are starting.
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
The user was manually toggling the status of the job rather than killing it before putting it on hold. This caused issues as eventually the run completed and then toggled the on hold job to SUCCESS. Need to educate the end users as to the proper way to kill / stop a job before putting it on hold.