- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 disable TLS 1.0 and 1.1
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to debug failed Automation Suite installations
- How to disable TX 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
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- ArgoCD goes into progressing state after first installation
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs

Automation Suite installation guide
dbo
and read
. Both tables store data from Orchestrator databases and pass data between each other. Over time, tables store a large amount
of data that can impact database performance. You can free up space by removing data that is not relevant or outdated.
The estimated threshold for storing historical data is set to
- 200 million RobotLogs
- 100 million QueueItemEvents
- 100 million JobEvents
- 20 million QueueItems
- 20 million Job
[dbo].Jobs
, [dbo].JobEvents
, [dbo].QueueItems
, [dbo].QueueItemEvents
, [dbo].RobotLogs
tables, or just the [dbo].RobotLogs
.
PROCEDURE
[read].[Delete_Insights_Data_Read]
and PROCEDURE
[read].[Delete_Process_Logs_Read]
scripts, the Insights module needs to be
disabled.
- Scripts with the
_DBO
suffix are used to delete data from DBO schema tables, - Scripts with the
_Read
suffix are used to delete data from Read schema tables. - Large-sized batches might impact the speed of execution. Consider using the default batch size, which is set to 100000.
PROCEDURE [read].[Delete_Insights_Data_Read]
and
PROCEDURE [read].[Delete_Process_Logs_Read]
scripts, the Insights module
needs to be disabled.
Jobs
, JobEvents
, QueueItems
, QueueItemEvents
, RobotLogs
) for a cut-off timestamp.
SQL Stored Procedures | Parameter | Description |
---|---|---|
Delete_Insights_Data_DBO |
| Delete data from [dbo].[Jobs] ,
[dbo].[JobEvents] , [dbo].[QueueItems] , [dbo].[QueueItemEvents] , [dbo].[RobotLogs] tables based on a cut-off timestamp.
|
Delete_Insights_Data_Read | N/A | Truncate [read].Jobs , [read].JobEvents ,[read].QueueItems , [read].QueueItemEvents , [read].RobotLogs tables.
|
The Insights Dashboard widgets are available again after SQL Stored Procedure 1 has finished, and the data has been backfilled. Keep in mind that the backfill process may take hours to complete given that you have a large amount of data.
Delete_Insights_Data_DBO
SQL Script, it creates a QueueItems.IX_CreationTime
nonclustered index with the purpose of making future executions faster.
Generate and save this SQL Stored Procedure to delete RobotsLogs based on ProcessNames and Tenant ID.
SQL Stored Procedures | Parameter | Description |
---|---|---|
Delete_Process_Logs_DBO |
The Orchestrator process name.
Tenant ID is required as two tenants might run processes with identical names.
Delete data in batches of 100000. See Considerations. | Delete data from [dbo].[RobotLogs] table by ProcessName and Tenant ID.
|
Delete_Process_Logs_Read |
| Truncate [read].RobotLogs table.
|