Robotic Process Automation - Robot Agent and Robot

• Robot Agent Logs path- In case of issues, refer the logs present at the location <<AssistEdge>>\client-tools \AutomationRuntime\RobotAgent\Logs\ AssistEdge_Agent.log
• Robot Logs path- In case of issues, refer the logs present at the location <<AssistEdge>>\client-tools \AutomationRuntime\RobotAgent\ Robots\<<RobotName>>\Logs\AssistEdge_SE.log
• Robot Agent not visible at Control Tower. Verify the MQConfiguration.xml details present under <<AssistEdge>>\client-tools \AutomationRuntime\ RobotAgent\Configurations\MQConfiguration.xml. Exchange name mentioned in Subscription queue nodes must be present in RabbitMQ.
• Robot Agent/Robot connection status as Red. Verify the
  <<AssistEdge>>\client-tools \AutomationRuntime\RobotAgent\Configurations\MQConfiguration.xml file under Configurations folder and verify if the RabbitMQ server details are correct.
• Invalid Request/ Process name not present in Profile. Ensure that the Robot is once run in the upgrade mode via the Control Tower/Robot Agent Upgrade button so that the latest profile-related data is downloaded.
• Robot in error state automatically after few failures. Verify the <<AssistEdge>>\client-tools \AutomationRuntime\RobotAgent\ Robots\\<<RobotName>>\Configurations\RobotDetails.xml node MaxAutomationFailuresAllowed value. In case the number of Automation failures reaches this number, the Robot automatically disconnects from the queue. Edit this number and restart the Agent.
• Issue with adding robot via the agent. Verify that the master robot copy path is correctly configured in agent and correct ProductVersion.xml file is present in the master copy of the robot from where agent is configured to download the robot locally. In case the ProductVersion.xml is missing, a Robot instance is added to Agent, however, robot installation stands in an incorrect state. During download, if any files are missing from the robot, verify if these files are listed in ProductVersion.xml of the master copy of the robot and files are present in the master copy at the correct location as captured in ProductVersion.xml.
• Applications can be launched when required to run a process on the first search request by setting the ‘EnableDelayedAppLaunch’ key to ‘True’ in the RoboSE config file. If this feature is enabled on a robot, the robot starts up without launching the applications which are part of the profiles for which the robot is being launched. Application that is part of a specific process will be launched when the first search request from Load Generator is picked up by the robot. If the application has been closed externally then Robot will auto-detect and re-launch the application on the subsequent search request. Please note that this feature does not close the application.
• Issue with Robot starting and get the following error logs “Error occurred while loading credential from Generic credential manager”.Refer the following link :
  https://www.dell.com/support/article/in/en/indhs1/sln316438/windows-credential-manager-stops-working-with-error-code-0x80070003?lang=en