Business Process list is slow · WorkFusion Documentation

When a Business Process (BP) in Control Tower is slow, investigate the following:

Check installation directory or installation disc performance

The installation directory might be full, or you might have installation disc performance issues. To test, try to copy one file to the same location but within another directory. If the copying takes much time, you have found the cause of your BP issue.

Check frequency of Data Purge or disc cleanup

You can also face BP performance problems if you fail to keep up with the required frequency of Data Purges or disc cleanups. Cross-check with the team if they run Data Purges regularly (for instance, delete unused BPs and remove old data that are > X days).

Delay in running RPA task

Check socket connections. Adjusting the socket value to 5000 can help to increase the performance.

C:\RPA\bot-agent\conf\bot-agent-unit.yml
socket:5000

Other component issue

BEP Agent servers can run out of virtual memory. As a result, BEP Agents fail to spin up for more Workers, and the Mesos cluster fails to launch new Workers due to the resource availability issue.

Check the status of all BEP Agents and the BEP Agents' load.

The recommended solution is to add one more BEP server to cope with the increased load due to additional BPs in the environment.

Slow network

Check by connecting to other networks. Cross-check if other users are also facing the issue or only specific people.

In the browser, press F12 to open Developer tools, go to the Network tab, and check the latency.

Network latency or internal component failure

A lost connection between components (for instance, Secrets Vault accessibility) can also cause slowdown issues.

Deadlocks in MS SQL can downgrade the performance of the system. If the issue cause is a deadlock, proceed as suggested below:

Add indexes to tables, or check the table size and utilization.

Based on the response given for the query below, consult with the DB team and get back to support if it's an indexing issue or any other.

   select
    s.name as SchemaName
    , t.name as TableName
    , p.rows as rows
    , sum(a.total_pages) * 8 as TotalSpace_KB
    , cast(round(((sum(a.total_pages) * 8) / 1024.00), 2) AS numeric(36, 2)) as TotalSpace_MB
    , sum(a.used_pages) * 8 as UsedSpace_KB
    , cast(round(((sum(a.used_pages) * 8) / 1024.00), 2) AS numeric(36, 2)) as UsedSpace_MB
    , (sum(a.total_pages) - sum(a.used_pages)) * 8 as UnusedSpace_KB
    , cast(round(((sum(a.total_pages) - sum(a.used_pages)) * 8) / 1024.00, 2) as numeric(36, 2)) as UnusedSpace_MB
    from sys.tables t with (nolock)
    join sys.indexes i with (nolock) on t.OBJECT_ID = i.object_id
    join sys.partitions p with (nolock) on i.object_id = p.object_id and i.index_id = p.index_id
    join sys.allocation_units a with (nolock) on p.partition_id = a.container_id
    left join sys.schemas s with (nolock) on t.schema_id = s.schema_id
    where t.is_ms_shipped = 0
    group by t.Name, s.Name, p.Rows
    order by TotalSpace_MB desc, t.Name

If, based on the instructions above, you failed to resolve the issue, create a support ticket.

View also: