- Release notes
- Before you begin
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Root cause analysis
- Simulating automation potential
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Customizing dashboards
- Publishing Dashboards
- App templates
- Notifications
- Additional resources
Process Mining
Basic troubleshooting guide
The purpose of this Troubleshooting page is to serve as a knowledge base for common problems faced or questions asked when using 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.
This section describes how to manually stop the data run from the database in case of a failing data run.
Follow these steps.
-
Retrieve the App ID of the process app for which you want to cancel the data run. Check outProcess App properties.
-
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]=3where <app ID> should be replaced with the App ID retrieved in Step 1.The following illustration shows an example. -
Refresh Process Mining Portal page.
-
Upload data for the process app.
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.
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>iptables -t nat -A PREROUTING -d <sql server IP> -dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port><sql server IP> and <sql server
port> with your respective SQL Server IP address and port number.
This command should be run as a root user or a sudo user.
To make the connectivity available from node level as well, an additional rule in the output chain is required:
iptables -t nat -A OUTPUT -p tcp -d <sql server IP> --dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>iptables -t nat -A OUTPUT -p tcp -d <sql server IP> --dport 1433 -j DNAT --to-destination <sql server ip>:<sql server port>iptables commands needs to be executed on all the nodes of the
cluster.
To make the IP table rules persistent, run the following command:
iptables-save > /etc/sysconfig/iptables
systemctl enable iptablesiptables-save > /etc/sysconfig/iptables
systemctl enable iptablesMake sure to configure the process app security. Check out Configuring process app security.
app_security_mode from system_managed to single_account.
