AnsweredAssumed Answered

Conditional Start Resource Use?

Question asked by loganjhall on May 26, 2016
Latest reply on May 31, 2016 by loganjhall

Greeting everyone,

 

Is there a detailed explanation regarding the differences between using a Nintex "Conditional" start vs building the condition into the workflow? We have been told that using the "Conditional" start option causes performance issues due to Nintex even receivers. This link was provided to us as a reference.

https://community.nintex.com/community/build-your-own/blog/2014/09/23/best-practices-for-reusable-workflow-templates

 

More specifically, is there a performance loss/gain using the "Conditional" start option for a "when modified" workflow that is associated with a List? Our team was under the impression that it was less resource intensive to use this option as the workflow wouldn't start. begin consuming resources, and be queued in the orchestration engine. We thought that this option was included into Nintex to allow workflows to be more efficient with resources by not running a workflow if not required. Having a workflow start and complete, even if it didn't perform any actions, would be more resource intensive.

 

If you can, please infer and describe the hypothetical relationship that exists between Nintex even receivers and performance degradation. Could anyone clarify this? I've included a few screen shots as well.

Condition.PNG

Condition_WF.PNG

Outcomes