16 docs tagged with "Business Process execution"

To back up a Business Process, follow the steps below, depending on the Work.AI version you are using.

The issues related to component malfunctions include the following:

Issues related to Control Tower (CT) performance include slow step transition, slow result processing, and the like. In general, slow CT jobs can result from high memory consumption (swap) and CPU utilization on the CT side.

An increasing number of database locks leads to Business Process (BP) performance degradation regardless of the BP complexity.

Control Tower (CT) can work slow due to high load on the MS SQL end, slow queries, deadlocks.

Code-related exceptions

Scheduler failure

To confirm and investigate an issue related to poor RPA server performance, act as follows:

You can observe delays in task execution due to tasks waiting long for a free Worker in a cluster or delays in Worker starts due to cluster resources utilized by other task types, thus being insufficient.

When no other circumstances change but the bot code, you can suspect that Business Process (BP) issues and slow BP execution are related to the Bot Task development. Potential root causes in the bot code are as follows:

Slow task processing can result from increased data volumes or a new document with a different structure introduced for processing.

Bots are executed on a separate Java Virtual Machine (JVM). As a result, a stop or pause action for a Business Process (BP) cleans up all queues for this BP and does not allow the Worker to start processing a new task from the main Worker queue. However, it doesn't kill the Worker already processing the task from the BP, and execution of the Bot Task continues till the very end, even if you stop or pause the BP.

[BEP] [Tasks by Worker type] Total tasks

[BEP] [Tasks Flow] Tasks Submitted

[BEP] [Tasks Time by Stage] By BP instance

[BEP] [Tasks Time by Stage] By BP Steps