Scheduled workflow to get Escalated Tasks and long-running Instances

  • 27 March 2024
  • 0 replies

Userlevel 1
Badge +5

I wanted to share a few workflows I developed to help in maintenance of running instances and tasks.  I will include the exported workflow keys so you can import them.


Once configured and published, the workflows will run daily to generate a report that is emailed to you or to a user to identify any instances running longer then X days or any tasks that have been “escalated” so that you can ensure someone follows up and completes those assigned tasks and running instances.


Here are the workflows:

  1. Component - Get Escalated Tasks
  2. Component - Get Instances Older than X Days
  3. Dispatcher - Get Escalated Tasks and Instances Older than X Days

For workflow 1, here is the key for import



For workflow 2, here is the key for import



For workflow 3, here is the key for import



Unfortunately, these keys expire at 30 Mar 2024 - 11:02 AM but I can re-generate for you them upon request.  Make sure to import #1 and #2 first before #3, because #3 calls both #1 and #2.


Here are more details on creating, editing and running these workflows.


Workflow #3 (the “Dispatcher”) runs on a daily scheduled start trigger.  It has a “Run parallel paths” action so that you can have it monitor multiple workflows.  In each path, you can have it call the 2 component workflows and send an email of the output from the workflow.


Workflow #3

Be sure to update this workflow and tell it the name of the workflow that you want to monitor. 


Component workflow #1 uses a Get Tasks action that needs a “Nintex Workflow Cloud” connection that requires a Client ID and Client Secret (generated from the tenant settings page under “Apps and tokens”). I have it check for “Active” status tasks.


It does a Loop for Each, then a Run If to check if it matches the workflow name, then Loop for Each task assignment, then Run if the Status is Escalated, and if so, append to a text string some of the task details.

Workflow #1


Component workflow #2 uses a Get Workflow Instances action of Status = “Running” and Loops for Each. It checks if the workflow name matches the input, then uses an action “Call a web service” to call the Nintex web API.  See this link for details -


You will need a “Bearer” token which is again found in Apps and Tokens.


The workflow runs some Query JSON to parse the results and then appends the instance data to a text string for output.

Workflow #2


I hope this helps you monitor for workflows and assigned tasks that need attention.

0 replies

Be the first to reply!