Top

Discovering suspended workflows with Microsoft Flow

In my daily work over business processes in Office 365, specifically in SharePoint Online, one thing annoys me the most – namely the lack of mechanisms to inform me that the workflow has hung up – that it is in a “Suspended” state.

The solution for that issue is not provided by Microsoft or Nintex – the company with which products I have been working for a quite long time. There are only workarounds, but they are inadequate, and I wanted to be able to react proactively and not reactively to any flow suspension event.

Nintex Pricing Revised

Nintex licensing models revised

Nintex subscription based pricing model is evolving since the beginning (since July 2016, when it was first announced). In January 2017 it has had it’s first major update. That time Nintex introduced such changes, as:

  1. No more workflow action limits (before it was 50 per workflow)
  2. Increased allocation of Dev/Test Workflows and Forms
  3. The new Grace Period Policy allowing customers to use Nintex for 60 days without being charged
  4. The Nintex Cloud Accelerator Program (NCAP) was introduced
  5. Small workflows (5 or less actions, no “Start a workflow” action inside) are not counted