Run a robot without internet connection. Is possible?

Hello friends!

We have an opportunity for automation but it differs somewhat from the standard we use today in our processes (unattended robots).

Basically, we will need to develop a robot that will be assisted when the local internet network goes down. Basically, the entire process to be performed by the robot is in offline tools. Is there any kind of license that works without an internet connection (to validate with the orchestrator?)? The idea is for the user to execute whenever there is no such connection.

It is important to remember that I tried the assisted robot license, but it still needs the connection with the orchestrator to link the processes.

image

Thanks.

Hi @_userdoleandro ,

An Unattended Robot needs to be all the time connected to Orchestrator in order to run.

An Attended Robot doesn’t require an Orchestrator connection in order to run. You can publish your RPA processes locally (not on Orchetrator) and you can use the attended robot to run them.

As long as your RPA process doesn’t need to connect to internet and, you are using an Attended Robot, then I see no problem to make an automation working without an internet connection

The following topic might help you as well: Attended vs Unattended Robots

Best regards,
Marius

1 Like

Hi @_userdoleandro ,
You can run the process only in studio(dev environment) without an internet connection for every other thing you need to connect to the internet and orchestrator . Even in studio , if you want to add remove a package , you need internet. so internet is a prerequisite.

1 Like

@shetanshudhar

This is not exactly correct. It is possible to have your Studio licensed locally on air-gapped systems without an issue. You could also have private / local package feeds as well (to install the packages)

@_userdoleandro Could you clarify your scenario? It is totally possible to set up an on-premise Orchestrator that will be available only within your company’s network and that could then control your robots even without access to the public internet.

But please share some details about your scenario, because I am not sure if that is your use-case.

2 Likes

Hi @loginerror.

We issue invoices in Brazil, where our ERP is integrated with the vehicle weighing system. This integration does not depend on any RPA. As the flow of vehicles is high and any time wasted by any failure in this integration or internet drop can generate financial losses, we need a solution where we can make these emissions faster (because without the internet, the process is automatic and becomes manual) and to place an assisted robot so that the teams execute it whenever it is necessary in contingency. RPA would basically do what that integration does today.

We will then need to carry out RPA executions with a scenario where there will not even be internet connectivity, even an OFFLINE execution. From what we tested, even in assisted licenses there is a need to validate it together with the orchestrator whenever it is necessary to execute (print of the post).

Hi @_userdoleandro,

Yes, I agree with @loginerror. A UiPath Studio robot can run both with or without internet.

When you want an airgap automation, UiPath allows both Attended (Logged in User triggered) and Unattended (Task manager trigger or localhost triggered) automation of any robot built via UiPath Studio.

Every Studio or Robot installation ships with the UiRobot.exe both in Community and Enterprise versions. This .exe file can start any .xaml file.

An example:

"C:\Users\%username%\AppData\Local\UiPath\app-20.10.2\UiRobot.exe" execute --file "C:\Users\%username%\Documents\UiPath\ForumAnswers\IEnumerableUiElement.xaml"

I have pseudo codes here in this thread for robots to be triggered from .net or task manager: SCHEDULING THROUGH TASK MANAGER - #5 by jeevith

In your case, probably the robot process can be triggered by the staff at the vehicle weighing port. A simple button GUI in any programming language can be linked to start your robot process.

The only draw back of such automations are that there is no way of having an overview of what happened during robot executions. You will still get access to execution logs in the individual machines (because Nlog logs to a given local log file), but this would mean that to know what exceptions occurred, the developers will need access to the robot logs, which may be cumbersome.

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.