@StephenTyson i’d suggest raising this with Nintex Support(support@nintex.com) if you haven’t already. They would be best to help identify what may be happening in your environment to cause this issue.

Nintex Support does not have a clue. They wouldn’t even attempt to troubleshoot, stating it’s a Microsoft problem when their timer jobs are removed after running the PSConfig wizard.   Nintex support is useless. 

​@StephenTyson We have raised several cases on this issue too last year. They weren’t able to help us either. We narrowed down the issue to servers which have SP Min-Role which does not contain APP or WFE Role like DC or Search Servers and running PSConfig.

​@MarcTrankalis  I was seeing the exact same issue, PSConfig on the Search or DC servers removed the timer jobs,  
 I think I have resolved the issue, Next patch cycle I will test my findings.   

After running updates and the PSConfig wizard, the Nintex Schedular jobs disappeared, I then reapplied the latest Nintex update.  After applying the Nintex update, I ran the PSConfig wizard on all servers and the schedular jobs still remained. Today as a test I ran the PSConfig wizard on the DC server in dev and the schedular jobs are still there.  This months patch cycle will allow me to validate. I’ll keep this thread updated with my findings.   

​@MarcTrankalis  I applied SP updates in the dev farm yesterday,  the issue is still prevalent.  After the first PSConfig was ran on the DC server the schedular jobs disappeared.  I added them back and ran the PSConfig wizard on one of the APP servers and the jobs remained,  not until I ran the PSConfig wizard on the search server did the jobs disappear again.    Nintex says it is a Microsoft issue and refuse to try and discover the cause of this issue.  The support tech I was working with was using a single server farm and could not reproduce the issue.  You would think as much money as Nintex brings in they would setup a mini role farm to thoroughly troubleshoot any issues a customer reports.   We just got a new Nintex Account Director, he wants to setup a meeting. I think I will bring this issue to light with him.  If you are aware of any other people experiencing this same issue send them to this thread. 

​@StephenTyson Did this issue get any progress by any chance? only 9 months till its deprecated anyway… sigh...

​@MarcTrankalis  I have been working with Microsoft and Nintex support for the past couple of months, implementing a suggested fix today recommended by Nintex to see if the issue gets resolved. I will follow-up with the recommended action once I have ran the updates.  Microsoft support bailed on the issue once they found out Nintex was working on it.  

I stand corrected, After voicing some complaints to our Nintex Rep, we finally got a Nintex support person that actually knows what they are doing and not reading from a script.  

​@MarcTrankalis  I forgot to add, my support guy at Nintex was able to reproduce the issue after he built out a mini role farm in SE. 

​@MarcTrankalis 

Support gave me a script to get Nintex forms working again immediately after running PSConfig on all servers,  

-----------------From Support:-------------------------

“To elaborate, when you interact with Nintex Forms in any capacity, one of the categories it logs under is 'Nintex Common'. Therefore, if you do something as simple as open a form, it attempts to log under this category that is non-existent. To replace this category after a SharePoint CU, you can run the following lines in the SharePoint Management Shell; I suggest running 1 line at a time: “

Add-Type -AssemblyName "Nintex.Administration, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" 
$bindingFlags = 'static','nonpublic','instance' 
$method = >Nintex.Administration.Common.ULS].GetMethod('get_Local', $bindingFlags) 
$uls = $method.Invoke($null, $null) 
$uls.Update() 
$uls.Farm.Update() 
 

Once this is done, 'Nintex Common' should exist again, and Nintex Forms should start working immediately. 

There's a bit of a delay on the Development team's end due to conflicting priorities, but I believe we have solid evidence and are on the right path. 

---------------End of Nintex Support Text------------------

We are getting closer to a solution.   I doubt Nintex is going to completely abandon Nintex forms and workflow on prem. There are too many customers who are heavily vested in the product and K2 still needs a lot more development work imo.  

Hi, we have same problem - mini role ShP SE farm, after installing last Microsoft security update and running PSConfig all Nintex timer jobs disappeared.

We recovered ScheduledWorkflows timer job via nwadmin (https://help.nintex.com/en-US/nintexSE/current/sp2019/NWAdmin/InstallTimerJob.htm) and have opened support ticket with Nintex but it's absolutely desperate - AI-generated answers that don't make sense.

Hi, thanks to Jamie’s workarround: 

there are steps how to return all missing timer jobs to place: just reapply Nintex license code.

No comment.

Michal