Basic troubleshooting guide

Introduction

The purpose of this Troubleshooting page is to serve as a knowledge base for common problems faced or questions asked when using UiPath® Process Mining. It does not provide a complete list of all problems you may encounter, but is intended to provide guidance with the most common issues. If you encounter any issues that are not covered here, feel free to reach out to UiPath® Technical Support.

How to cancel a data run from the database

This section describes how to manually stop the data run from the database in case of a failing ingestion.

Follow these steps.

1. Retrieve the App ID of the process app for which you want to cancel the data run. See Process App properties.

2. Contact you database administrator to run the following SQL query in the AutomationSuite_ProcessMining_Metadata database:

   with Ingestion_tbl as (select top 1 * from dbo.Ingestions where AppId = '<app ID>' and [Status] = 1 order by LastUpdated desc) update Ingestion_tbl set [Status]=3 where <app ID> should be replaced with the App ID retrieved in Step 1.
   See the illustration below for an example.

   

3. Refresh Process Mining Portal page.

4. Upload data for the process app.

How to add an IP table rule to use SQL Server port 1433

Only the default SQL Server port 1433 can be used for the Airflow metadata SQL server database AutomationSuite_ProcessMining_Metadata. If your organization policies or firewall rules do not allow using port 1433, you can redirect incoming traffic directed at port 1433 of the SQL Server IP address to a new SQL Server IP and port.

Use the following Linux command to add a nat rule in the IP tables PREROUTING chain:

iptables -t nat -A PREROUTING -d <sql server IP> -dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>

Replace <sql server IP> and <sql server port> with your respective SQL Server IP address and port number.

Note:

This command should be run as a root user or a sudo user.

When creating a process app the status stays in Creating app

Possible cause

The database service is not set correctly during installation or upgrade.

Solution

Make sure to configure the process app security. See Configuring process app security.

Note:

If you cannot update the SQL server permission, it is recommended to change the app_security_mode from system_managed to single_account.