- 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
- Customizing process apps
- App templates
- Additional resources
- Out-of-the-box Tags and Due dates
- Editing data transformations in a local environment
- Setting up a local test environment
- Designing an event log
- Extending the SAP Ariba extraction tool
- Performance characteristics
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 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.
This section describes how to manually stop the data run from the database in case of a failing ingestion.
Follow these steps.
-
Retrieve the App ID of the process app for which you want to cancel the data run. See Process 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.See the illustration below for 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.
Make sure to configure the process app security. See Configuring process app security.
app_security_mode from system_managed to single_account.
