Hi there,
I would suggest doing some testing - in this case I would disable the Web Service call to see if everything moved along as expected with out it. The For Each action isn't bound by Safe Looping like the Loop action so it being the reason for the pause would surprise me. I think that maybe your Web Service is taking long to respond or even timing out - if you could post some screen shots to give us a better look at what you have going on inside the For Each that would help as well.
Thanks
Indeed, disabling safe looping and republishing the workflow solved the issue.
Since this is not a production environment and used only for demos, there is no issue with safety here.
The one odd thing about all of this is that the trick did not apply for the "Waif for" action. When i specify 1 minute in for this action, it still takes around 5 minutes to execute.
Yes, that is because the default is usually about 5 minutes - it simply overrides the 1 minute you specified in your wait.
I'm not sure what you mean by "default is 5 minutes".
Where can I change it ?
Thanks!
Hi,
When you use the "Wait for" action, the current process no longer runs the workflow. It's relayed to the Timer job and the pause depends on its next execution, which is by default every 5 mn.
Manfred Lauer gave you a good reference on how to change it.
Can you post a screenshot of your workflow?