14. Testing and Troubleshooting

Exceptions

The Exceptions tab has a list of every error encountered as the task engine processes task trees. The most recent exception is listed at the top. Clicking on an exception will reveal more details. Place the instance Id of the request in the Source ID to track if you are not coming from an exception. You can get the Id either from the URL when you get to the confirmation page of the request or from the Completed Customer Submission Console - Submission Instance ID field.

The exception details include information about the location of the error, and the stack trace from the handler. However, the most informative information is probably 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' = "info@kineticdata.com"

You can also click on the Source ID or Tree ID and you will be taken to the related Executions tab.

Executions

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.