Nintex workflow scheduler job stuck on running. I checked the Central Admin to check if there are more than one job scheduled, but it has only one. Can someone can please shed some light on this issue.
We too facing the similar issue. We usually restarting the Timer Service on the respected server, to fix this temporarily. You too can try this if it helps.
Team, any one got permanent fix for this? We have 126.96.36.199 version.
In my environment I have even tried to do an iisreset but that scheduler just got stuck and its not moving.
So I did timer, in both wfe environments, I did iisreset and no luck
Is your workflow history list getting too large?
Thank you for the response, I will check. It could be getting larger
Will get back to you. I will create new history and use it instead of the old one and see if there are any differences.
I have just had a look burkslm and I have created a new workflow and create a new workflow history and it behaves the same way so I guess the history is not really the issue but maybe it could be part of it.
I've been told you aren't supposed to allow the history to get too large so using that new history is a great start to working on your problem. You may want to purge the old history.
Even I have the same problem and would like to know a few details. Nintex workflow scheduler timer job is stuck at 0%
I do remember that I can purge the Nintex workflow data from Central Admin, by applying filters like delete older than specific date, completed workflow's data only. I understood that we need to clear this data as this lists size is increasing day by day.
But I would like to know how Nintex Workflow Scheduler timer job is related to the size of workflow history list. I'm under impression that this timer job is searching all over sites on farm to fetch for Scheduled Site workflows and it will trigger them. Am I making sense? Can you please explain me in detail.
I would review the following about the details of the scheduler job, if this doesn't help you then you may want to contact support. Scheduled workflows and the Nintex Workflow Scheduler timer job
You can go into the workflow history list and change the settings so they delete after so many days too. It also helps that you don't have all of your workflows assigned to the same history list. My employer wants all the workflows to have different history lists and not to have all actions logged to reduce the size.
That's a good practice. There's governance, and then there's over-regulation. It's hard sometimes to find the balance.
I'd recommend taking a look at the workflows you are having issues with and seeing if they have anything in common, as I've seen some design/logic mistakes actually cause the timer service to lock up. I've seen one bad workflow almost cause a traffic jam effect as well, which ended in up in the timer service being locked up.
Retrieving data ...