"Hello! This Is Robot" Prompt Causing The Robot To Time Out

News Knowledge Base
1

Why does Windows Security popup "Hello! This is Robot", causes Robot to time out?

Issue Description:
During Robot execution, some users confront an error that causes the Robot to hang and ultimately time out. The error interfaces manifest as "Hello! This is Robot" and "Please provide _________access credentials". These messages are produced by the "Request Credential" activity commonly executed in older versions of the Robot Enterprise Framework.


Root Cause:
The error typically occurs when the program can't retrieve the necessary credentials due to either a lack of network connection or an absent corresponding asset. This error can be attributed to two potential root causes:

  1. A network glitch
  2. A system policy affecting the Robot machine's ability to communicate with Orchestrator.

Resolution: To solve this issue, consider implementing the following changes:

  1. Adjust the child processing to avoid reliance on the "Request Credential" activity. Opt for the "Get Credential" activity as a substitute. In case this activity also encounters issues, raise an Application Exception and proceed with further records processing.

  2. Update the Robot Credentials in the Windows Security Manager across all Robot VMs. This action ensures the Robot can retrieve the Credentials at the Windows level in case of failure to fetch the credentials from the Orchestrator.

Note: Remember, if still working with a project that was created from ReFramework, there will be a request to enter the necessary credentials using the "Request Credential" activity whenever the program fails in obtaining the asset. Therefore, it is crucial to keep these troubleshooting tips in mind.

Additional Troubleshooting:
If the issue persists even after implementing the solutions recommended above, it may be necessary to seek further assistance. Do this by opening a Support Ticket with UiPath where professionals will continue troubleshooting. When opening the Support Ticket, it is essential that the following files and details are included to successfully identify and resolve the issue:


Details Required:

  1. A sample Project that reproduces the error, or the 'project.json' file of your currently malfunctioning Process
  2. A Diagnostic Tool Report retrieved from the Robot machine where the process error occurred
  3. Fiddler /Wireshark traces obtained while reproducing the issue
  4. The Estimated Time of the problem's occurrence.