- Before you begin
- Managing access
- 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
- Process simulation
- Root cause analysis (Preview)
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Process Insights (preview)
- Creating apps
- Loading data
- Transforming data
- Autopilot for SQL (preview)
- Structure of transformations
- Tips for writing SQL
- Exporting and importing transformations
- Viewing the data run logs
- Merging event logs
- Configuring Tags
- Configuring Due dates
- Configuring fields for Automation potential
- Activity Configuration: Defining activity order
- Making the transformations available in dashboards
- Data models
- Adding and editing processes
- Customizing dashboards
- Publishing process apps
- App templates
- Notifications
- Additional resources
Common issues with uploading data, including unexpected encoding errors and steps for setting UTF-8 with Windows-style CR/LF line endings.
Message: utf-8 codec can't decode byte <byte> in position <position>: Invalid start byte
The following message is displayed in the data run log.
Possible cause
One or more input files you uploaded have an unexpected encoding.
Solution
Set the encoding to UTF-8 and set CR/LF end of line characters (Windows style).
You can change these settings in a file editor. For example in Notepad++.
- Open the datasource file in Notepad++.
- Go to Edit -> EOL Conversion and select Windows CR LF.
- Go to Encoding and select Convert to UTF-8.
- Save the file.
Message: File upload failed due to the following error: Network error
When uploading data using .csv or .tsv files, the following error message can occur:
Possible cause
Incorrect or missing HTTPS certificate.
Solution
The HTTPS certificate used by the BLOB store must be valid in your browser. Check the error and make sure to get the appropriate certificates.
- Go the Process Mining portal and press F12 to open the Developer tools.
Check the Console and Network tabs for the ERR: CERT_AUTHORITY_INVALID error. This indicates an error with the trust of the HTTPS certificate. The following illustration shows an example.
- Contact your IT department to install the certificate chain of the authority listed in the error and to add it to the trusted certificate store in operating system for all user that will be using the system. For example, pmcprddatawesa.blob.core.windows.net.
Message: Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly, including the signature.
This message is displayed during an ingestion.
Possible cause
The SAS uri (Azure Shared Access Signature) used to upload the data is no longer valid.
Solution
Update your upload configuration with the current SAS uri for the process app.
- Open the Process Mining portal.
- Locate the process app for which the ingestion failed.
- Open the upload data dialog for the upload type you use.
- Copy the SAS uri.
- Replace the SAS uri in your upload configuration with the copied value.
Refer to Retrieving the credentials for the Azure blob storage for details on obtaining the SAS uri.
- Message: utf-8 codec can't decode byte <byte> in position <position>: Invalid start byte
- Possible cause
- Solution
- Message: File upload failed due to the following error: Network error
- Possible cause
- Solution
- Message: Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly, including the signature.
- Possible cause
- Solution