Orchestrator fail over

Help
1

Hi All,
I have few queries on fail over mechanism of orchestrator. consider the below environment setup.

Environment Setup:

  • around 10 attended robots licensed with concurrent user type connected to the orchestrator.
  • orchestrator deployed on-premises server.
  • Licenses are managed through orchestrator(as usual).
  • latest version of orchestrator and studio is used.
  • process/nupkg are developed to get the assets from a local source when orchestrator assets are not available.
  • transaction items are stored in files not in orchestrator queue.

Scenario 1:
while a process/nupkg is running on a robot,particular robot disconnected from orchestrator due some internal issue. what happens to the current running process? will it continue ?
(assume that robot not fetching any assets and transaction item from orchestrator)

Scenario 2:
If orchestrator is down, robots couldn’t connect to the orchestrator. then, what happens to the license which is allotted to a robot ? is that robot still licensed to run a standalone process / nupkg file ?

Scenario 3:
if Orcestrator is down, is that process packages which is allotted/ deployed from orchestrator will be available in robot tray ? If yes, could we run a process in a particular robot without connecting to orchestrator ?

Thanks & regrds,
Dushy

2 Likes
2

Hi ,

I am orchestrator admin in my organization and I will answer your questions as much as I know . correct me if I am wrong.

Scenario 1:
while a process/nupkg is running on a robot ,particular robot disconnected from orchestrator due some internal issue . what happens to the current running process? will it continue ?
( assume that robot not fetching any assets and transaction item from orchestrator )

Answer
If no asset or queue (not transaction) items, robot can continue. But processes with assets and queue data will get error .
If your transaction item in local file , will run I guess.

Scenario 2:
If orchestrator is down , robots couldn’t connect to the orchestrator. then, what happens to the license which is allotted to a robot ? is that robot still licensed to run a standalone process / nupkg file ?

Answer
No . Licenses are dead if you activated with allocated from orchestrator option.
Only ongoing processes will run. After that both studio and robot will die.

If you activate with standalone it is ok and you can still use stuido.

Scenario 3:
if Orcestrator is down , is that process packages which is allotted/ deployed from orchestrator will be available in robot tray ? If yes, could we run a process in a particular robot without connecting to orchestrator ?

No, robot tray will die also.

1 Like
3

Hi @ddrdushy1

It’s a good set of questions. Let’s take it one by one…

Scenario 1
Robot is always installed in your machine. The orchestrator is like the control center which controls the execution of tasks and manages the robots. So assume that orchestrator provided the run command to execute a particular package which is available in your machine. Since no orchestrator assets are used it will run without a problem. However if the robot is running a package which is deployed in orchestrator, then if the robot get disconnected from it, it will not know what are the next steps to Run because it no longer have access go the process it was running since it was deployed in orchestrator. Then it will run into errors and stop.

Scenario 2
If the license is taken from the orchestrator and if it get disconnected, Your robot and the studio does not get activated. However if there is a ongoing execution, it will complete without any issue. This depends on my previous answer though. However you will need to get the connection back to use Studio or the robot since the license is required for them to work.

Scenario 3
No. If the robot get disconnected, the local robot tray will not show any available processes and you will not be able to run any process through the tray

Hope it helps

1 Like
4

Thanks @Lahiru.Fernando & @Alvin,

I have another question, In scenario 1, when the robot continue the process, it will send log messages to orchestrator right? is it cause to error ? how UiPath agent update the logs to orchestrator ?

5

@ddrdushy1

I guess in this case it can’t update logs back to the orchestrator as it is disconnected.

1 Like
6

Thanks @lakshman,
Bcoz of that, running process will terminate or it will continue?

7

Hi @ddrdushy1

Yes. Like @lakshman mentioned, if the robot is disconnected, it will not be able to update the logs in orchestrator. However I don’t think that will cause an error and fail the entire execution. The point I’m trying to defend here is when we run a package through studio the logs are not added to orchestrator. But still it works. And as I remember these logs are saved locally. @lakshman bro correct me if I’m wrong about this point… I haven’t really tried it. So not too sure

1 Like
8

@Lahiru.Fernando

Yes if we are not connected to Orchestrator then logs will be saved in local machine and as we are running it from studio or robot.

2 Likes
9

thank you guys. @lakshman @Alvin @Lahiru.Fernando :clap:

1 Like
10

Its a good question. Helped me as well to refresh some of the points I learnt few weeks back… :slight_smile:

2 Likes