From what I was told, a number of NetConfig jobs scheduled to run in January somehow got reactivated recently, so stale changes got pushed. All NetConfig jobs have to go through an Approver group, so these jobs got approved either in Jan or recently or both times. Considering NetConfig jobs are set to be purged after 180 days, my questions are: What state could these jobs have been in, that they could be reactivated way past 180 days? If these jobs had run in January already, how did they manage to survive the 180-day purge? Does NetConfig job purge not delete jobs that are unapproved/pending/in draft mode? Do the Approvers get a second round of request for approval, when the jobs somehow get reactivated to run a second time? Are there any measures available to prevent a scenario like this from recurring?
Yeah, the patch applies to LMS 2.6 as well. A patch could be created. The resurrection is due to the state of JRM at the time the processes are restarted.