We have built a SP 2010 workflow solution in SP designer. Very basically, there are 10 steps in the workflow. Before and after each step, there are some custom elements, which we have coded in visual studio. Each step produces tasks for one or more users and on completion, moves the workflow on, after any custom activities.
We are experiencing so many issues with this solution that we can’t replicate as the issues occur somewhere inside the SP engine. We then have to hunt for the error in the ULS logs and, if it’s descriptive enough, we may be able to find a workaround. Other times the issue is just so random, often due to timing, we think.
I’m looking for someone to advise on a better architecture. My gut feeling is that the workflow engine itself should be coded entirely, and the code should just produce the sharepoint tasks (we can’t move away from the tasks needing to be SP tasks). At least then, we can catch and deal with any errors as opposed to them disappearing into the SP ether.
Am I going to be better off coding an entire workflow engine?