- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable NIC checksum offloading
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure After Certificate Update
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to Resize Objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Cannot Log in After Migration
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Connecting Task Mining application
This page walks you through the steps for connecting the Task Mining client to the Automation Suite instance.
For Task Mining specific requirements, please refer to the Task Mining client Hardware and software requirements (single-node evaluation and multi-node HA-ready production installations).
This is where you configure your project settings, including which team members will participate and which applications should be recorded.
In order for the invitation email notifications to be delivered, make sure to set up system email notifications.
In case system email notifications are not configured, users will still be successfully added to the project, however, they will not receive an email with the link to the desktop application and sign-in instructions, please make sure to communicate the instructions to users.
Follow the below steps to send an email invitation to selected user(s). The resulting email will contain instructions for each user to download and install Task Mining client application.
Each user you have specified will receive an email containing instructions and the link to download the Task Mining client.
This step is only required for the self-signed certificates, which are a default option during the installation.
More information can be found here: Configuring the certificates
If during installation you have opted in for a CA-trusted certificate you can skip this step.
Follow the same steps used to configure the DNS during installation of Automation Suite to make the FQDN of your Automation Suite installation accessible from the local machine.
Object store host (e.g., objectstore.dns-123.eastus.cloudapp.azure.com) is necessary for the following Task Mining flows:
- Task Mining client application requires the host to push captured data to the Admin Portal.
- Admin portal leverages the host to download data relevant for visualizing the analysis results.
If the host is not specified flows above will not work.
Install and run the Task Mining client application
- To make sure the certificate changes work, ensure your Service URL and the certificate used for the SSL are allowed in your company network (firewalls, proxy configuration, etc.).
- Make sure to paste the Service URL without the "/" at the end of the string, as it won’t work with the slash in the link.
Cannot find a UiPath® web service at the given address.
-
Please make sure that you can connect to the Task Mining service in Automation Suite using the browser of choice.
-
If you are, please follow through the following steps.
-
If the Task Mining service is not enabled - please make sure to proceed
-
If not - please make sure to capture the screen and make sure that prerequisites for connecting Task Mining client application (certificate installation, hosts file edit) are met.
-
- If there is any company to direct traffic through a proxy service - please make sure to configure the proxy service in Task Mining application explicitly.
- If the steps above didn’t help resolve the issue, please collect application logs and reach out for support.