I schedule the same WF 3 times a night with a List Limit of 100 on a Query List. There are 275 items in my list, thus the 3 iterations will loop thru 100, 100, and then 75 respectively for each iteration.
All 3 iterations of the WF run the desired tasks which is adding new records to the list, however every night we do get an "Error Status" under "My Running Workflows" for 2 of the iterations. Again though all the desired tasks within the WF ran for all 3 iterations.
Interestingly the last iteration (the one under 100) never gets an error. Do I get an error because I have set a list limit of 100 and my list is > 100 ? How do I cancel the error ?
Solved! Go to Solution.
what's the exact error?
Query list action limit shouldn't be a problem. I suspect problem is causing create item action. you my try to disable it and run the workflow that way, I expect workflow will run without a problem.
you will have to decrease number of loop iterations or apply a commit pending changes after each bunch of iterations (eg. 50)
it causes workflow execution is handed over from IIS worker process to the timer job process.
read this blog for details
This worked ! However, I am not sure why...I did read the link, but I was unclear why my Site Workflow now works with a Pause - is it due to perhaps my Site Collection had more than 15 Workflows running...
Why would having the Timer Job running the process make the difference for a Site Workflow. If the Timer forces it to run from the Content Database, where does the WF normally run from and why does that make a difference ?
Sorry for all the questions. Now that it works I suppose I could go on my merry way, but I want to understand why it now works.
eg. because there are applied different limits and restriction on worker and on timer job processes.
how much time did it take until workflow failed? wasn't it usually (approximately) the same time?
you may have eg. exceeded worker's request execution timeout