+5
Does anyone have any insight as to why, for my workflow, that when I use a set condition the workflow works flawless, but when I put in a state machine above it. it gets stuck on change state after the first change state. I can even put an email action on the yes side of condition and it will send the email but as soon as it hits the change state on either side, it just gets stuck. I tried searching the net and could not come up to a conclusion.
+5
I do have change states on all branches, whether referencing a state or end state. I talked with our admins and they state it would not be a timer job as it works without the change state.
Any other ideas?
+16
can you put the change state after your set condition like this:
+5
Same issue when nested under the condition.
+16
Why doesn't incoming submittal branch in your state machine not have a change state? It needs one.
+5
DOH!!!!.... that was an over sight this time around....uno momento por favor
+16
I've just read my poor English in that reply - bravo for understanding it!!
+5
Cassie,
The English was just fine. I redid the WF and ended up with same result the workflow just gets stuck.
+16
Ok so it goes down the left hand branch, sends the email and gets stuck? What is the pause for doing? Why do you need that?
Have you checked timer service is up and running? Does it change states after say 15 minutes?
+5
I was setting the pause due to, that when it works fine under the Set Condition with no State Machine, I was getting the Request Data before a notification, but I tried it without the pause and it still does the same. That is the second screenshot with the history(no pause).
+16
OK do me a favour please Pete; create a brand new workflow with just a state machine in it - give it three states each having a log to history of some arbitrary text and a change state like this:
Run it and see if it works. This way we can see whether anything else is impacting the performance.
The fact that the workflow works without the State Machine is exactly the reason it would be a timer job issue. Did you read the article I referenced?
+5
+16
Thirded (not sure that's a word but you get the idea)!
+5
Well I am back at step one. I appreciate your folks insight to a newbie. So all the research I have done is not in vain and makes me feel better I am not crazy as well as knowing IT just will not listen to me.
THANK YOU!!!!!
+7
Hi Pete,
This will probably not help at all, but we have two environments SharePoint 2010 and SharePoint 2013. We had the same issue with SharePoint 2013. built a workflow in the 2013 environment and it kept getting stuck. He also built this workflow in the 2010 environment and everything worked perfectly.
Back in 2013 we checked the safe looping setting on the central admin and that was fine and then we ended up restarting the timer job as well as IIS. We eventually ended up restart our whole SharePoint 2013 environment and the issue seemed to have gone away for now but without know what actually caused it.
I too believe its an environment issue. Without a state machine, what occurs with just a pause action. Does the workflow come out of a pause and continue without issue? What about using a loop? These can help to troubleshoot the environment.
Use the tips in the document linked earlier. Make sure there are SharePoint and Nintex patches applied where appropriate.
+16
Ooh good shout you could also try "start workflow" and see what happens with that.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
