Various types of information about the Bot Agent are captured in different log files. You can analyze these log files when the Bot Agent or a automation encounters an error and identify the root cause for that error.

Overview

The Bot Agent log files enable you to perform these actions:
  • Determine whether the automation execution was successfully
  • Identify issues that resulted in the automation failure
  • Determine if the device is properly connected with the Control Room

Log file locations

Node_Manager
Enables communication between Control Room and the registered Bot Runner device.

Bot Agent log files are available at /Library/Logs/AutomationAnywhere/NodeManager

For example, Control Room uses the Node_Manager to retrieve the status of a specific device, receive automation deployment messages, forward the status of the automation executions and so on.
Bot_Launcher
Captures information about the execution of an automation such as the operations performed, events triggered, and errors encountered by the automation.

Bot Launcher logs are available at ~<USERHOME>/Library/Logs/AutomationAnywhere/BotLauncher.

The filename now includes the name of the user running the automation on the Bot Runner. For a multi-user session machine, there will be an automation launcher log per user.

Log file configuration

To configure the different types of log files that can be collected from the devices connected to the Control Room, see Configure log collection.