We experienced a very disturbing issue with our workflows during design time. We have 4-5 bigger workflows (big as the number of action in the WF or the number of actions are not too big, but the task forms are Huge (lots of controls/repeting sections, etc). It's inside the limits. We can publish we can run them. BUT...
When a user with averege laptops (Intel i3/5, 4GB+ RAM, Win7, IE11) edits teh WF for a longer period (30 min to 2 hours) the WF Editor silently crashes...
- Flexi task deciesion brances mixed up for no good reason, or manual change
- Branhes shifts to left or a branch is unusabel anymore (can't add actions into that...)
- Task Forms disappear or on task form got overwritten with another one.
an similar unbelievable events... It's like the whole WF XML gets ruined.
My first idea was that the windows/IE runs out of memory and starts killing the processes inside and accidentally kills Nintex or something like that.
But happens the same with better laptops too... Any Limit to WF XML/FORM size? Unspoken Nintex limitations?
Has anybody experienced similar issues?
Thanks in advance!
Solved! Go to Solution.
since Nintex ist creating SharePoint 2010 Workflows, the same limitations as for regular SharePoint Workflows apply: Software boundaries and limits for SharePoint 2013
Moreover I know that Nintex only supports Workflows up to ~200 actions. Having more than 200 actions inside your workflow can cause problems (like WF can't be published anymore).
This is all I know about any limitations.
Thanks Philipp, I read a lot about this in teh past days and before too, It looks like the issue occurs when the workflow contains tasks with huge forms and you edit these forms. IE's memory consumption constatly increases and if it's above 1GB the crash likely occurs.
Eg.: I can't click on save workflow, or publish... Simply doesn't do anything. Very disturbing.
Generally speaking I can tell, that there's a kinda hard limit for Nintex workflow size. Which is fine, but sometimes it's really hard to swallow, when you have to tell the business user that their idea has to change (a lot), meanwhile you try to slice up their workflow.
Users have the above mentioned laptop/hardver/software resources and huge workflows:
Errors we experienced in design time:
I read a lot about performance, consideration, splitting up in the past months, pros and cons, etc. Now I can tell in our environment I find the limitations we have to follow to avoid future pain:
Maybe it's just us, we expect too much or we want too much. Situation is still the same. We have to overcome our issues.
Directions we took (every case is different, take slots of consideration and planning which is applicable):
Still not applicable perfectly on every workflow, sometimes it's against logic in a WF to cut into pieces because of extra 2-3 MB...
Sounds like you are having a lot of fun at the moment
Anyway, great post, will bookmark it as a reference for all boundaries/tresholds/limits so thanks for that!