We have a strange issue in one of our workflows. We're on Nintex 2007 version 1.1004 by the way.
Since we deployed a new version of an existing workflow, it fails in about 30% of all cases.
And weirdest of all: if it runs into an error, it's always at the same step number:
The error occurred every time at the same action: a 'Commit pending changes' action which doesn't do a whole lot.
So in an attempt to check if we some sort of timing issue, we added a 'Delay for...' action in front of it, delaying the workflow for 5 minutes.
After we published this adjustment, the workflows kept ending up in an Error status in about 30% of all cases.
And when we looked at the workflow history for one of these errors, the step that the workflow was stuck at was the 'Delay for...' action.
I don't see how a workflow can run into an error on a Delay action. Why could this be happening? It's now almost like the workflow fails at the same step number each time: it used to at the 'Commit pending changes', but after this step moved up one place because we put a 'Delay' in front of it, the error suddenly occurred at the 'Delay' step.
Could this perhaps be a SharePoint server issue? Something with the Timer service or Admin service.
Any suggestions very welcome!