Skip to main content

Back in the SP 2010 days I was told a best practice was to keep workflow size under 500Kb. Performance/reliability would begin to suffer beyond 500Kb. Does that hold true in SP 2016 and Nintex WF 2016 (both on-prem)?

I've seen many example of workflows on this site that clearly exceed 500Kb.

According to this thread "there is no restriction on the size of your workflow. However, you may start to see issues after 500k or 100 actions."


Hi Ken,

 is correct. In the most technical of terms, there is no "restriction" on workflow size but I can tell you from experience that if you go over .5Mb you will have problems. This is not a Nintex limitation but a SharePoint limitation. The errors will be intermittent and occur on random actions throughout the workflow making it frustratingly difficult to troubleshoot unless you know you are dealing with a size issue.

For additional information on Nintex, SharePoint and Workflow limitations, check out this link: https://community.nintex.com/docs/DOC-1513 


Patrick,

Would this apply to the SP 2013/16 release as well?


Yes, as far as I know, Microsoft has not made any changes to deal with this limitation so you will need to either split your larger workflows or work on simplifying your processes.

By the way, if you question is answered, please mark Roger's as correct as I only elaborated on his remarks.

Thanks!


Thanks you both for your responses!


I'm having problems with the Nintex workflow that is just 65 KB but has 146 actions. I'm using Nintex for Office 365. It's hard to split a workflow since in Nintex for O365 there is no way to pass parameters to other workflow and no User Defined Actions. But on the workflows larger than 120 items I'm consistently getting error messages: 

Error "Oops! Something went wrong ... ButtonPanel - handleXamleBuildError : SyntaxError: Invalid character"

 

I'm going to create a custom list to use it to pass parameters between workflows.


Reply