Heads-up on Office 365 Terminate workflow Instances and Terminate Current Workflow

Not applicable
1 3 3,408

Good news for those who are familiar with the Terminate Workflow action in Nintex Workflow on premise version, and are interested to migrate to Nintex Workflow for Office 365 or already started using it. The Terminate Workflow action is available with some additional enhancement compare to the on premise version; such as the ability to terminate site workflows.

Terminate Workflow Instances vs Terminate Current Workflow

There are some times during designing of a workflow, that as part of workflow logic it is required to end the process, under a specific condition. For example, if the task is not approved, you can use "Terminate current workflow" to end the workflow process.

As you can see there is no error or problem with the workflow, and we need to terminate the process intentionally, as part of the workflow design. In this scenario it is required to use Terminate Current Workflow action.

But there are some situations, especially when we are in a development environment, and workflow designers are working hard to design workflow logic every day, and at the same time testing is going on. As a result of negative testing, we might end up having lots of suspended workflows. Or maybe due to some issues with the SharePoint Environment, there are workflows which are not started and are stuck for a while, or many more scenarios which the workflow is not Active anymore, and we need an automation system to terminate them.

  In this case, "Terminate Workflow Instances" is really useful to terminate those inactive workflows, and terminate the instances. For example, there might be a list of items which is supposed to run a workflow on every new item created. On the first day there are 1000 new items created and 100 workflows out of 1000 are suspended due to user invalid inputs, and we need to terminate those workflows and re-run the new instances with correct inputs. Therefore what we need to do, is to simply create a new Nintex workflow, put a Query List action and Query XML action to get all list items, and then using a "Loop N times" action to loop on all the items, and finally terminate workflows using "Terminate Workflow Instances" action, if they are suspended or not-started.


Important Note!!

There is an option to terminate Running (active) workflows as well, which is enabled by default. This means, it will terminate any instance of the workflow, including those which are active. If you don't need to terminate running workflows, simple turn the option off in the Action's configuration.


Good luck.

Nintex Observer

I know this post is almost 5 years old now, but I just ran into this problem and this description is really not helpful. While it's great to give an overview of why the problem exists and some small hints about how to solve it, it would be exponentially more useful to your audience to put specific, illustrated details about how to configure each workflow action so that end users like myself can actually solve the problem. Why Nintex hasn't already solved this problem is equally as baffling.

Nintex Observer

Exactly - there is no description about how to configure the actions... Pity, I would gladly use it in my daily work. 

Community Manager Community Manager
Community Manager

@natiweg is the a particular part of the configuration that you need help with? These actions don't have a lot of configuration available, but happy to help if you can give some more context.

Screen Shot 2020-10-12 at 10.20.59 AM.png

Screen Shot 2020-10-12 at 10.21.59 AM.png