Robotic Process Automation – ControlTower

  1. ControlTower Logs path- In case of issues, refer the logs present at the following locations.

    <<AssistEdge>>\data\ControlTower\controltower.log

    In case of startup issues, check the following logs.

    <<AssistEdge>>\data\command\controltower.log
  2. In case the control tower is not visible, verify if the Control tower service is running using the ‘ae status’ command. If the control tower is down, use the ‘ae start controltower’ command to start the control tower.
  3. If the request is coming into RabbitMQ after all validations and is still not reaching RobotSE, verify if the consumer is disconnected from the queue. If yes, connect it again from the control tower.
  4. If agent or robot is not visible on the control tower, validate that txnStore, messaging and Vanguard are up and running.
  5. Control tower servers must be started in the following order – txnStore, messaging followed by Node server.
  6. In case of a very slow network connection, the robot can get created on the agent, but may not be reflected on the control tower. Users can check if the ‘IsSoft’ flag is set to 1 in the database table. If it’s 1, set it to 0.
  7. Robots In Error
  • While the robot is starting and is in authentication or sign-in state, it is moved to the Error tab. Only on the successful execution of the above actions, the robot is moved to the Running tab.
  • If a robot remains in the Error tab with the status ‘Robot Agent Communication Failure’. In this case, the robot must be restarted.
  • If Robot remains in the Error tab with the message ‘system error’, check the logs in the Robot folder on the specific machine.

    Notification - open items
  • If there is a robot configuration error (like incorrect or corrupt config files /incorrect service URL), the robot will move to the Error state, and no notifications are sent.
  1. Time interval between commands
    1. If a robot is running a lot of applications and is taking more time to disconnect or stop, the time interval must be configured accordingly. Time interval between commands for robot stop /start/schedule change is configured in config.yml.
  2. Robot Agent not visible in CT:
    1. If Robot/Agent is not visible in the Control Tower, check the RabbitMQ queues. Agent and robot health can be checked in the Automation Heartbeat component table in the database.

      FCFS Known Limitation:

      In FCFS scheduling mode, request order is maintained only if there is a reasonable time interval between requests. If re- quests are sent without any delay, the order of delivery to the robot for processing is altered.

      In a multi-profile mode, if requests are sent before a robot starts, the robot will start processing the same on starting, but the order of requests is not maintained.