Skip to main content

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 ?

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)

I added a commit pending charges (per 50 records) and it made it thru about 200 records and I got an error message "WF failed to start"  Any ideas

Try to add  pause action at the beginning (first) of the workflow.

1-Should I add the Pause at the beginning before the loop starts

2-What should be the amount of the Pause

place it as a very first action in the workflow.

1min is fine. note however it will wait until at least next timer job run, which is typically scheduled once in 5min.

What is the purpose of the pause and its correlation to the timer and commit pending action...

it causes workflow execution is handed over from IIS worker process to the timer job process.

read this blog for details

Defensive Workflow Design Part 4 - Slow Down and Speed Up 

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

Thanks..I will check tomorrrow...I assume I will find out previously it failed each day after the same amount of time...I will then I assume close out the question...Many thanks..

For some reason when I click on Workflow History it says working on it for about 3 minutes and then I get an error...Any suggestions as I was hoping to look at the WF History prior to your suggested change to see if it failed around the same amount of time each time...thx

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings