I have a list (List A) in my SharePoint 2010 site that has many paused workflows in it. They are all waiting for a specific date at which point they move to another list (List B). When items are created in List A a workflow is supposed to fire
that reads a date field for that list item and pauses until that date. However, it seems that the workflow does not always fire. Currently there are 1,040 items in List A.
To try to solve this I re-created the workflow on List A that is supposed to fire on item creation. Most of the time it works, in fact it's never failed me while testing it. However, when users start to make use of it there are failures. Although it works
most of the time, I'll have a about 5-15 failures a night, out of about 60-90 processed items.
It's important to note that these are not registering a failure code of any kind - they are just not starting at all. Because of this I'm having a very difficult time troubleshooting. So far I've just been starting the failed ones manually every day, and
they work fine - not cool.
I have other workflows on the site that never fail, only this one. All workflows have been created with SPD, I don't have Visual Studio.
Is 1,040 paused workflows too many? Could that cause a sporatic issue like this? Should I be coding a solution here instead of pausing that many
View Complete Post