Finding the Root Cause of Runtime Errors

3 minutes to read Download PDF Edit

1 Introduction

This how to will show you how to find the information necessary to locate the root cause of a runtime error. The message displayed in the application is often vague and non-descript. Depending on the environment in which the error occurred, there are two methods for finding this information.

This how-to will teach you how to do the following:

  • Find the root cause of runtime errors via two methods

2 Method #1 – Using the Modeler

If the application is deployed from the Modeler, the information is located in the console:

When an error occurs, a line with a red font will appear in the console. Double-clicking on this line brings up the VIew Log Line Details pop-up window:

There are three key pieces of information in this window:

  1. The microflow and action where the error occurred.
  2. The type of error that occurred.
  3. The expression in which the error occurred.

With these three pieces of information, you should be able to find the cause of the error. If you cannot determine the cause from this information, you can put a break point in the specified microflow and debug the situation.

3 Method #2 – Using the Application Logs

If the application is deployed from the service console or in the cloud, the information is available in the application logs.

Go to the section of the log that corresponds to the time of the error. There will be a number of lines in that timeframe that have ERROR – after the timestamp. These are the lines of the log file that contain the necessary information. There are three key pieces of information here:

  1. The microflow and action where the error occurred.
  2. The type of error that occurred.
  3. The expression in which the error occurred.

With these three pieces of information, you shouold be able to find the cause of the error. If you cannot determine the cause from this information, you can put in a break point in the specified microflow and debug the situation.