We are having an issue with occasional Tasks being created by a WF that have a blank Assigned to field. Solution consists of:
- A form with a People picker field that allows the user to select and validate the Authoriser name.
- An Auto-start-on-New SP Designer workflow runs that does a "Collect Data from User action" and assigns the Task to the Authoriser.
Unfortunately, although this worked fine during dev and test, now the solution is live and we are having 150-200 requests per day, we are finding that the WF occasionally fails to fill in the Assigned To details when it creates the Task. (approx 8 failures
per 200 requests, ie 4%).
As SharePoint already has the User data field, I am confused why this might fail, and there is no obvious pattern (same auth, 4 work OK then 1 failure).
Does SP contact the AD again when it creates the Task?
Anything else I should investigate? any suggested fix / work-arounds?
View Complete Post