Hi ​@angelachengmuni,

Sorry to hear you are having this issue.
I have not head about any issues with the latest CU from Microsoft but I am guessing that you may have updated from an old CU and have installed older updates that caused this issue.
To help solve which CU issue you have I suggest that you contact Nintex support via the customer portal.

You have stated that this is a Nintex workflow issue but you will find that SharePoint designer workflows that have pauses in them will show the same behaviour as this is a MS issue that affects their workflow engine that Nintex also uses.

We are using Version 5.2.2.0 and all previous updates are in web.config file.

Nintex workflows (State Machine workflow and Site Workflows) are not run as expected after December 2024 patch update

Hi ​@angelachengmuni,

I understand how challenging it can be to navigate the complexities of the SharePoint workflow engine. I genuinely recommend reaching out to Nintex support, as they will be better equipped to assist you with this issue. I'm sorry that we can't resolve this in this forum.

Any updates on this?  We applied the following updates last night and now some (not all) workflows are “failing to start”

2024-12 cumulative updates KB5048661
sql server 2019 RTM cumulative update (CU)KB504235
Security update for Microsof SharePoint server 2019 Core (KB5002657) farm deployment
Security update for Microsof SharePoint server 2019 Language Pack (KB5002664) farm deployment
Microsoft Defienter antivirus KB2267602 amd KB2267602

We also have got problems with some (continuously running) workflows which are halted at the ‘pause’ step in the workflow. These problems did occur after the December Sharepoint CU. We  used Nintex 5.2.4.10 for SP 2019 Workflow and Forms. We upgraded to 5.2.11.10 and did also the January Sharepoint CU but the problem still occurs. We also tried this fix but did not help: 
https://learn.microsoft.com/en-us/answers/questions/2140927/latest-(dec2024)-round-of-sharepoint-2019-patching

So in the end the problem still occurs, as Simon mentioned, it looks like a Sharepoint issue instead of a Nintex issue. I think we have to add the correct authorizedType in the config. If i have an update i will place it here, if anybody has more ideas, please share that information here. Thanks!

I was able to get ours fixed.  I followed the instructions included in this document:

It is weird that this same thing happened in December 2022 and how our workflows continued to run after December 2022 without applying this fix then.  Once I deleted the AuthorizedTypes node in the OWSTIMER.EXE.CONFIG file and restarted the service, all my workflows started running correctly.  Make sure you backup the config file before making the change.

Good Morning,

we have after the CU Update DEC 24 also a problem with scheduled Workflows.

Do you have a solution so far?

Thanks :-)

“ The xxx workflow has ended unexpectedly.

Workflow xxx was canceled by Systemkonto.”

I have the same error. Please help.

I was able to fix it by following the instructions in the document I linked to in my previous post.

If you have entries in OWSTIMER.EXE.CONFIG, when you update to the latest CU the issue can reoccur as it will sync the entries and break again. It recommended to use web.config to manage entries to prevent this as mentioned down the bottom in the link here. There has been a few similar issues and we provide a fix in our next release as mentioned in the release for the latest version here.