cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
rdalle
Nintex Newbie

State machine and safe looping - can you clarify Nintex behavior ?

Hi !

I've read several threads around state machine and safe looping, but it seems like my question is a little bit different (or I didn't find the right thread, my apologies in that case).

Let's say I have a State Machine configured with branch A, B, C, D, E

Branch A can lead to B or D depending on the task result

Branch B can lead to C or D depending on the task result

Branch C can lead to D or E depending on the task result

Branch D can lead to Branch A, B, or C depending on the task result

Branch E is the final branch and has a change state "Exit state machine"

The situation I've been able to see is the following

When Branch A, B, or C finishes, there's a delay before starting next branch. I suppose it is due to safe looping.

When Branch D finishes, there is NO delay before branch A, B, or C starts again ==> No safe looping I guess.

My question is : Why ?

Thank you for your help

0 Kudos
Reply
3 Replies
greenawayr
Nintex Newbie

Re: State machine and safe looping - can you clarify Nintex behavior ?

I might be wrong but I don't believe safe looping applies to the State Machine.

I believe Safe Looping applies to your FOR EACH type actions, and is designed to stop rapid repetition of actions and hogging server resource. The State Machine is subject to SharePoint timer processes and so delays between state transitions are caused by how long the workflow waits for that timer job to run.

BUT, I'm not certain on any of this, so hopefully someone can confirm this or offer a more factual explanation for you.

0 Kudos
Reply
rdalle
Nintex Newbie

Re: State machine and safe looping - can you clarify Nintex behavior ?

Thank you Ryan for your participation on this thread. 

According to this following thread, safe looping applies to state machine

 

0 Kudos
Reply
greenawayr
Nintex Newbie

Re: State machine and safe looping - can you clarify Nintex behavior ?

ok, I would still imagine it's something to do with the timer job that's running to change the states, but not sure. ‌ might be able to give us a bit more insight.

Reply