Skip to main content
Nintex Community Menu Bar

Terminate workflows automatically


Hi all,

in our SP 2016 farm we have many Nintex workfows running. Unfortunately, many users ignore the message that a workflow has ended unexpectedly. My question is now, why is there a "error" status and why do you always have to end a workflow manually - terminate this workflow? Furthermore, is there a setting (maybe with PowerShell or in the CA) that a workflow terminates itself after it ends unexpectedly.

I hope I get some answers because this is bothering me for quite a while now.

 

BR, Alex

Translate
Did this topic help you find an answer to your question?

Forum|alt.badge.img+12

Rather terminating the errored workflows, I would suggest to find the root cause for erroring the workflows. Issue could be with workflow logic, or  Nintex Services or Nintex related timer jobs.

Translate

Forum|alt.badge.img+5
  • July 13, 2021

 

Here is a script to terminate all workflows on task items with a due date of more than 7 days in the future.

 

#Get Site COllection
$siteCollection = Get-SPSite "http://sharepoint.dev.com/sites/site/"

#Your Shaeproint Site URL
$spWeb = Get-SPWeb "http://sharepoint.dev.com/sites/site/sub-site";
$spWeb.AllowUnsafeUpdates = $true;
$WFManager=$Web.site.WorkFlowManager

$deadline = (get-date).AddDays(7)

foreach($subSite in $spWeb.Webs)
{
$subSite.Title
$subSite.AllowUnsafeUpdates = $true
$WFManager=$subSite.site.WorkFlowManager
$list = $subSite.Lists["Requirements"]

foreach ($listItem in $list.Items)
{
$duedate = [datetime]$listItem["Due Date"]
if ($duedate -gt $deadline)
{
foreach ($workflow in $listItem.Workflows)
{
# Write-Host "internal State: " $workflow.InternalState
if ($workflow.InternalState -ne "Completed")
{
# Cancel Workflow
[Microsoft.SharePoint.Workflow.SPWorkflowManager]::CancelWorkflow($workflow);

# start workflow
$WFAssociation = $list.WorkFlowAssociations | where {$_.Name -Like "*Requirement Reminders"}
Write-Host "wf association $WFAssociation"
$WFManager.StartWorkFlow($item,$WFAssociation,$WFAssociation.AssociationData)
}
}

}

}

$subSite.Dispose()
}

$spWeb.Dispose()

Translate

Hi,

that's not that easy: we also have users which have no programming skills who also build worklfows or are allowd to bulid them. Unfortunately, those WFs often have some design flaws or they don't test the WF well and so errors occure once in a while. The WFs designed by the IT department run like a charm - so its not timer related.

 

BR, Alex

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings