Bot Runner configuration and settings
- Updated: 2024/11/25
Bot Runner configuration and settings
Real-time processing refers to scenarios where users expect immediate results while waiting for a response. Automation Anywhere supports real-time use cases, provided that the processing time per document aligns with user expectations.
If the existing processing speed meets your requirements, you can use the recommendations above. Ensure that sufficient Bot Runners are available to handle the real-time load without delays. High-spike use cases involve irregular loads, where volumes peak at specific times. For these situations, configure a device pool to dynamically allocate bot runners as needed and repurpose them when the spike subsides.
Bot Runner configuration and settings
For optimal performance of Bot Runners in Document Automation use cases, we recommend using CPU-optimized virtual machines (VMs) with SSD storage. Specifically, the c5ad.xlarge EC2 instance on AWS, equipped with 4 CPU cores and 8 GB of memory, provides a well-balanced configuration for Bot Runners. Comparable instances from other cloud providers can also be used to achieve similar results.
Bot Runner settings
There are several Bot Runner settings available, but the following configurations are particularly critical for ensuring optimal performance.
- Autologin timeout
- Navigate to and set it to 170 seconds to avoid timeout failures.
- Auto-login configuration
- Navigate to and select the Leave the session unlocked option for all the options to maintain sessions for unattended Bot Runners.
- Device deployment settings
-
- Navigate to .
- Select the appropriate device.
- On the Edit device page, click the Deployments tab.
- Set the Device type to Regular for default deployments.
- Bot Runner user association
- In , avoid associating users with specific devices to maximize the flexibility of the device pool during runtime.