workflow默认会在60天后被自动清理掉。你可以看看是不是这个原因
可以禁用这个功能
http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/4ca5dd5c-bce7-43fd-af29-7379227ca6fb/
http://msdn.microsoft.com/en-us/library/dd441390(v=office.12).aspx
Workflow AutoCleanUpDays
Although the AutoCleanUpDays setting is not directly related to performance, it is important enough to the overall workflow environment to warrant discussion. It is also largely misunderstood and, depending on whom you ask, either does too much or not nearly
enough.
The purpose of the AutoCleanUpDays setting is to remove the association between a workflow instance and its history entries and to clear out the workflow instances and tasks. It does not actually remove the entries from the History List. By default, this
cleanup happens 60 days after a workflow instance has completed, but that timeframe is configurable.
The primary impact that cleanup has on performance is that the workflow status page loads faster when users browse to it because it has fewer items to query against from the task list. As mentioned previously, cleanup does not actually remove the items from
the History List, so it has no impact on the 2000-item limit. A side effect of this process is that the SharePoint content database becomes less cluttered (specifically some of the workflow tables), which may help with performance in very large workflow environments
where hundreds of thousands of workflow instances may be or may have been running.
You can set the AutoCleanUpDays value for a particular workflow template by adding the following nodes to the element manifest (typically workflow.xml). Replace
xxxx with the appropriate number of days.
<Elements ...>
<Workflow ...>
<MetaData ...>
<AutoCleanUpDays>xxxx</AutoCleanUpDays>
</MetaData>
</Workflow>
</Elements>
Every new association based on this template now uses the specified AutoCleanUpDays value. Naturally, this change does not affect existing workflows, the built-in workflows, or SharePoint Designer workflows (which do not use an element manifest file). In
these cases, you must run code to change the AutoCleanUpDays property of the
SPWorkflowAssociation object. The challenge is that you need to run this code periodically to properly update associations that were added after you ran the code initially.
One final point on this subject is that you should not consider the Workflow History list to be an audit log. If you need that capability, there are other options.
上善若水
Lambert Qin [秦磊] | 博客(Blog): SharePoint in My Eyes
中文 /
LinkedInPosting is provided "AS IS" with no warranties, and confers no rights.
