Showing results for 
Search instead for 
Did you mean: 

Task Escalation comes to Office 365

Nintex Employee
Nintex Employee
7 12 5,263

Remember those days when you have an automated business process and it sits there waiting for someone to do something or approve a task and they just won't?  Those days are over.  Task Escalation has made it to Nintex Workflow for Office 365.

When you open Nintex Workflow from a List, you'll see this cool popup letting you know that you have new functionality :


There are few things that have changed, but we'll be focusing on the Task Escalation part in this post.

The Task Escalation functionality is available in the Assign a Task action and the Start a Task Process action.  I do want to briefly mention that the user interface for those actions have changed slightly.  The sections have new names.  But it shouldn't be anything too surprising.  The purpose of which, is to make for a better user experience.

But what is really important, is that we now have a new section called "Escalate and auto-complete options".


The default behavior, as you can see above, is "Do nothing".  Which really means, if someone is slacking off and not responding to a task, your business process is on hold.

The other options are :

  • Escalate to person or group
  • Auto-complete the task

Escalate to person or group


I have to say, that one of my favorite parts about this, is that you can specify when a task is going to be escalated.  But you don't have to have a static value.  Most likely, you'll be using an item field or a variable.  Probably a DateTime variable.  That opens up the usage here dramatically.  Not only can you specify when to escalate, but you can also add business or calendar days.  That's impressive and again, make this functionality so much more powerful.

Don't forget about the option to information the original participants.  You'll have the option to customize the email too.  This may actually help them in future tasks, knowing that if they don't respond to a task in a reasonable amount of time, it will get escalated to the CEO!!!.

As part of this process, if you're going to set an expectation that the task will be responded to within a set amount of time, make sure you update the email those goes to the original participant, to they are aware.  Also, don't forget to use Reminders!!.

Auto-complete the task

This is a piece of functionality where there is a person or group that is expected to respond. If they don't, there's no one else to go to.  So we want to automatically complete the task, and that could be Approve, Reject or one of the other outcomes.  The rest of the configuration is the same as the previous option.


There is help available for all new functionality.

Help for Assign a Task

Help for Start a Task Process


Interested in a trial of the Nintex Workflow for Office 365 product?

How about a demo of the Nintex products for Office 365?

If you have any questions about this new functionality, please feel free to leave a comment on this post.

Nintex Newbie

Nice post...Wonder how many people will get the escalation right the first time :)

Not applicable

Nice work. Saves us a lot of work, actions and loops.

A pity it wasn't available earlier, would have saved us a lot of time.

Is there a overview of which actions Nintex is working on?

Not applicable

Hey Emiel, task escalations are available in the following actions:

Not applicable

I was wondering on which actions the team is working, like what is in the pipeline (new actions, modification on existing actions).

Not applicable

Hi Emiel, we don't share roadmaps, as they are always subject to change depending on customer's needs, partner requests etc, and we don't want you to rely on this for project plannings! We have releases every month, and there are exciting things coming in the next few months. We announce each product release in the Product Release Announcements​, which you can subscribe to, or have a look at the Nintex Workflow for Office 365 - Release Notes​, which describes each release.

Nintex Newbie

There is also our UserVoice site where feature requests can be viewed / added and our Product Team will communicate which requests will be acted on.

Check it out here:

Not applicable

You say not to forget about reminders.  Is there a function to notify the original assignee that the task is coming due?  Multiple times?

Nintex Newbie

When you setup the task you can add a reminder for the assigner as well if you want.  I would treat this as a similar reminder that you setup and just pull in the initiator.

Nintex Newbie

I'm currently testing a workflow with a "Start a Task Process" action and an escalation (to myself) but it doesn't escalate. I'm choosing the escalation date as today for the sake of testing but it never sends the escalation email, however the workflow status is "complete". Is it only supposed to escalate after the due date even if I program it otherwise?

Nintex Newbie


AS you've discovered, the escalation is only triggered when the regular procedure is met... you may have to set it up with a due date in the past to see if that triggers it. Also, I have not fully tested that, but escalation usually goes to a different user so not sure if you can escalate to yourself. Again I have not tested that specifically, but worth a shot.

Nintex Newbie


I've tried what you suggested to test but it still isn't working. I have a testing buddy who I assign all the tasks to so that I can be the Escalation assignee but I haven't received one escalation yet. I've tried using the due date (today) as the escalation trigger, I've tried the due date plus 15 minutes, but I'm still not receiving any escalation emails. The workflow also seems to register as "complete" the minute it sends the first task notification. It doesn't wait for the escalation period. How can I test this without waiting for a day to know if the escalation will work (or not)?

Nintex Newbie

Good Day,

I have a scenario where I use multiple approvers for a task. 1 Approver approves and the 2nd one don't. The task escalates after 24 hours. When the new approver, after escalation, rejects the task, it follows the approval leg of the workflow. Seems that outcomes are ignored if there were mulitple approvers assigned to the task originally. Can someone share some light on this please. Nintex support could not. Many thanks