I recently inherited an existing environment (SP 2010) using Nintex. When I browse the logs, I am seeing entries with the following values:
Start Time: 4/10/2013 9:09 AM Last Action: 4/10/2013 9:12 AM Duration: 1651 days Idle Time: 1651 days
I am assuming this workflow is no longer active nor is it doing anything useful. How does one terminate/kill this and other workflows similar to this? Of course not knowing the details of the workflow, any default fallout for terminating a workflow after so long?
Thanks in advance!
You can always manually open the running workflow instance and kill the instance by hitting end workflow:
In general I wouldn't terminate workflows just because they hit a specific idle time but you can use the know your workflow script (Know Your Workflow) or Nintex Hawkeye to find idling workflows and find a reason for it on a workflow by workflow basis.
Would that be helpful?
The "Know your workflow" is exactly what I am missing. As stated in the initial post, I inherited this and this is my first exposure to Nintex. I will take a look and reply.
Thanks for the reply.
When I dig into one of the workflows, I select "Terminate this workflow" and I receive a popup stating, "Object doesn't suppot propety or method 'createNode'" with only an OK option. I also noticed in the workflow information box for the Item: value it show Cannot find list item.
I see this starting to "snow ball".
It seems there are some fragments of workflows for items that have been deleted. This can happen if users delete lists and items that still have running workflows without ending those workflows first.
What I would try first is to purge those workflow fragments. Purging can be done by heading for Central Administration -> Nintex Workflow Management -> Purge workflow data and hit query with leaving the selection to Where the list or library has been deleted.
If if found fragments hit Purge afterwards. If no fragments remain, the result should look like this:
Do you still see the same error afterwards?
However, you should absolutely know what you're doing when going through this. In doubt I'd consult a Nintex partner and do this together on site.