16 docs tagged with "Bot Task"

To analyze task execution, follow the steps below:

The Master Agent, Unit Agent, and Workers connect via REST API during a reconnect procedure. The Worker application requests the Unit Agent in the RoboticsFlowPlugin plugin. The Unit Agent requests the Master Agent. To configure a reconnection timeout for a Worker and Unit Agent, follow the instructions below.

The Workflow Designer tab opens slowly. In addition, the following Bot Task manipulations inside Workflow Designer are also slow:

Code-related exceptions

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:

When your Business Process is stuck at a step and doesn't process further, the reason for the behavior is likely a Bot Source configuration.

After clicking Advanced > Bot Configurations > Import from the Repository, the message about the import start is shown, however, an artifact is not loaded. To identify the root cause for the issue, it is necessary to check the configuration.

Typically modified values

The table below lists of useful Java Virtual Machine (JVM) properties you can add, remove, or change to achieve specific purposes.

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

[BEP] [Tasks by worker] Input Task

Cannot launch bots locally because of duplicated dependencies