Robot's Randomly becoming Unresponsive

Help Orchestrator
,
1

Hi. I am working on an private instance of Orchestrator that we host in Azure. For the past week, we have randomly started receiving error notifications that robots are becoming unresponsive. They automatically reconnect, but then every 2 to 5 minutes, it alerts me again. It happens to all the robots? The robots themselves seem to be operating as normal. Any idea why this could be happening?

2

Hello @neacailh!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

3

Hi @neacailh,
There might be many reasons. Unstable connection, some proxy issues and so on. I would recommend to open ticket for our Technical Support.

4

I have observed such case - virtual machine (Amazon Workspace), user is not logged and UiPath assistant is minimized.
If we maximize assistant, it does not happen, also for case if nobody is logged in VM.

5

Make sure your robot is installed from MSI package so it’s available under system mode.

6

Replying here in case our situation helps others. I went many rounds with UiPath support on this problem providing one type of log after another and they finally revealed it was a bug in the version of Orchestrator we were on (2021.10 and 2022.10).

They provided the following workaround:

  1. Navigate to Tenant >> Manage access
  2. Select a robot account
  3. Click the 3 dots and click edit.
  4. Click Robot Setup (Or Unattended Setup depending on your version)
  5. Uncheck the “Run only one job at a time” checkbox.
  6. Click the update button