Application issues

Introduction

When developing your application, you may introduce application issues that cause it to produce an incorrect or unexpected result, or unintended behavior, now or in time.

For example, by adding a reference to an attribute that does not exist (anymore), by using a function that will be deprecated in a next version of the UiPath Process Mining platform, or by simply making a typo in an expression.

To optimize your application, it is important to keep your application free from errors. The UiPath Process Mining platform offers functionality to detect issues and potential problems in your application early, which enables you to find and resolve them fast and easy. In general, you should be able to solve the application issues in your application.

Application issues versus conflicts

When working on an application as a team, your workspace may become outdated because of commits made by others to the same branch.

Before you can commit your changes, you must update your workspace to the latest revision to include these changes. When updating while your workspace contains local modifications, it might happen that these changes conflict with changes someone else has committed. In this case, your application will contain conflicts that need to be resolved before you can commit.

Note: Conflicts are not the same as application issues.

Overview of Application issues

Application issues are grouped into categories. Below is an overview of the different categories of issues in order of importance.

Element	Description
A	Error
B	Deprecated function
C	Warning
D	Informational message

Errors

An error refers to a mistake in your application that might affect what will be displayed on a chart in the released version of your application.

For example, when you have made a typo in an expression, the result will give error values. Or, sorting a join table on an attribute that is not available in the table, will cause the result to be unsorted.

In general, errors do not depend on the data, although this is possible in severe cases. In most cases, data-dependent issues are categorized as informational messages. Examples of data-dependent errors are data input files that cannot be found or an out-of-memory error during computation of a join. In these cases, there will be no output data that can be displayed on the chart.

To ensure the correct working of your application, you must resolve all errors before you release your application.

Note: Some of the errors found in the scan may also block the cache run.

Deprecated Functions

A deprecated function refers to a feature that is about to be replaced by a new better alternative in a future release of UiPath Process Mining. To prevent you from using a removed feature, it will be marked as ‘deprecated’ first.

A deprecated function will remain available for a specified time frame, to enable you to update your applications.

A deprecated function in the Issues pane shows you in what version the feature will become unavailable. Make sure that you resolve the deprecated function by replacing it with the new feature before you upgrade to the specified release. In case you are unsure how to resolve a specific deprecated function, please contact UiPath Process Mining support.

Warnings

A warning refers to a potential problem in your application that does not affect the result displayed in your released application.

It is advised to resolve any warnings to prevent any potential future problems. For example, the message “Multiple attribute's names only differ by implicit aliases and will break unions: + unionname,”, indicates that currently, the application works fine, but things will break once the user starts using the referred unions.

However, if it is acceptable for now, you can decide to ignore the message until it leads to an actual problem. For example, the “Aggregate is filtered by a read-only filter: + controlname” message, do not affect the displayed result. (If the filter is read-only, it cannot be used to filter data.)

Informational Messages

An Informational message is a message that contains helpful information on improving your application or keeping it free from errors.

Since informational messages do not refer to critical errors, you may choose to resolve informational messages, but this does not affect the working of your application. For example, the “Attribute has error values x out of y” message that appears if one of the values contains faulty input.

Some informational messages can be data-dependent. For example, if you use an attribute as a divisor which may result in a divide by zero.

Note: In some cases, it might not be possible to resolve the informational message.