Task Manager Console
The Exceptions and Executions links on the Task Management Console provide the most information while troubleshooting and monitoring task processes.
The Exceptions tab has a list of every error encountered as the task engine processes task trees with the most recent exception listed at the top. Clicking on an exception reveals more details.
Exception detail includes information about the location of the error, and the stack trace from the handler. However, the most informative text is listed under cause. This section will have any specific error messages that the creator of the handler included. For example, this is the cause from the image above:
CAUSE: RuntimeError: There was no KS_SAMPLE_People record to match the qualification: 'Email' = "email@example.com"
You can also click on the Source ID or Tree ID and you will be taken to the related Executions tab.
The executions tab includes information on both the errors and the instances and triggers. Triggers are created both to initiate the Start node, and complete (restart) deferred nodes. Instances are created as the task engine processes individual nodes.
Triggers and task instances are displayed with the most recent at the top of the list. Tree details has a drop-down list that lets you toggle between exceptions and tree execution information.
To search for your execution, you need to first select the Source Root (Kinetic Request) and then either select form the list or enter the Submission Id of your specific request.
One important difference with exceptions on the executions tab is that you have the ability to retry the node, or skip the error and continue processing.
Depending on the type of exception, you will have an opportunity to retry or skip the node and continue processing the task tree.
Example of Exception with the Retry/Skip option
After fixing whatever has caused the error, select retry (or Skip), add Resolution Notes (required) and click the Resolve Exception button.
The task engine will create a new trigger and try to continue processing the tree, while the failed trigger is placed into a Status of handled.
Failures on Connectors cannot be retried, but most other errors in nodes can.
Activity Twelve - cause an exception