With Nintex Workflow 2010 running a second timer job on the SharePoint Application server would cause our workflows to fail. We are considering an upgrade to SharePoint 2013 and would like to know if Nintex Workflow 2013 still has the one timer job limitation. We are concerned this issue will limit the scalability of the new SharePoint Farm.
Page 1 / 1
Hi Lee
Do you refer to the issue where enabling the workflow timer job service on an application server that is not running the web front end role causes issues?
Resolving this is being worked on at the moment, for both 2010 and 2013. We anticipate it resolved in our next major release later this year.
James
Yes this is the issue I am talking about. Thanks for the information. I would appreciate it if you would follow up on this post when the issue is resolved.
Hi Lee, I need to correct my statement about it being in the release later this year. Its actually scheduled for the first release next year.
regards
James
But if you have mulitple front end servers, you can run the timer job on each.
Reply
View our Community Site Map
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.