SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am in the process of upgrading our SharePoint environment from 2010 to 2013. As you may know SharePoint only keeps workflow associations around for a period of 60 days, after which they're deleted. We currently use these associations coupled with the workflow history for auditing purposes, or, if they've been deleted we can run an 'Activity Duration Report' for the workflow to show all the approvals that were done. The 'Activity Duration Report' was available if you went to a library's workflow settings, followed by 'Workflow Reports'.

I've done a test upgrade to our environment and seen these workflow reports have now disappeared under workflow settings (apparently Microsoft removed them in 2013). Now that we can't use these reports anymore, I'm wondering what to do next. I know we can increase the AutoCleanupDays to a larger value than 60 days using PowerShell, however the script would need to be ran every time a new document library is created, which will be quite cumbersome. Is there any other solutions to keep this history or at least go back after 60 days?

share|improve this question
up vote 0 down vote accepted

You can use the same script in your description, but have it run nightly, to pick up any new document libraries.

Also, if you perform regular backups to your environment, you should be able to track any audit trail back to the date/user that is needed. Whenever you need to see an audit trail, restore to a test site collection, and that workflow and workflow history will be there for viewing.

If you are tight on space, you can do an export of the workflow history to store it somewhere (even back on SharePoint). Write a script that will traverse through the workflow history and capture it all, let's say 30 days worth, then store it somewhere for auditing purposes.

share|improve this answer
Thanks Mike, I had a feeling I was going to have to run that script on a timer but wanted to see what my other options were. I guess monthly would be sufficient since the associations are kept around for 60 days by default. – Hoff Jul 23 '14 at 13:30
Yes! Put a script on a task scheduler to run on weekends. – Mike Jul 23 '14 at 14:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.