Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

Task Tree Pausing

Pausing a specific task tree.


Pausing a task tree will prevent the engine from processing any part of the task tree.  The processing of that tree will wait until resumed (whether manually or via a task handler).

What are the benefits of this feature?

The primary benefit of pausing task trees is allowing the front end process of gathering requests to continue while the back-end process is not active for development, enhancements, or another reason.

When to use this feature?

Task tree pausing is useful when a process needs to be updated but access to the services should still be allowed.  In this case pausing the tree will hold all processing until the tree is ready, but we can still allow access to service items.

It could also be used to prevent handler or tree errors while troubleshooting problems by preventing any new processing from taking place until the tree is unpaused and processing is resumed.


Task tree pausing affects all processing that would happen in the paused tree.

If a trigger would start processing of a tree, and if the engine detects that the tree is paused, it will create a paused trigger and stop instead of  processing any nodes.  The trigger created should be identical to the one that attempted to start the processing except it will have a Paused status.  It will also contain a special flag that indicates to the engine that it was generated as a result of a paused tree.  This is done so that you may select and resume specific executions to ensure things are working before unpausing the tree and resuming all of the paused processing.

Note about deferred tasks.  Task tree pausing comes into effect whenever any processing would be done.  It is no matter whether the action is create, update, or complete.  Imagine that a task tree was paused after an instance was created for a deferred node.  Now an update or complete trigger is created for that instance.  When the engine begins to process that trigger, it detects that the tree is paused, creates a paused trigger, and stops processing.

Pausing a Task Tree

To pause a task tree, navigate to the Tasks tab in the Service Catalog Console.  Select the tree to be paused and click the modify button.  Change the status to Paused and click save.

Unpausing a Task Tree

To unpause a task tree, return to the Tasks tab in the Service Catalog Console.  Select the paused tree and click the modify button.  Change the status back to Active and click save.

Even though the task tree is now unpaused, all of the processing that was paused for this tree will still be waiting to be resumed.  Processing can be resumed two ways.  Manually updating the task trigger record, changing the status from Paused to Unpaused.  Or, the recommended method, using the Kinetic Task Trigger Resume handler.  Click the link below to download and see more details about the use of this handler.

Resume Paused Task Triggers