Issues with UiPath automation deployment

Dear all, I am feeling somewhat frustrated and need to know if it is just me or if this is a common issue with this job. It happens quite often that I create an automation, deploy it on other machines, and they do not respond. It seems as if they cannot find the selector I use. Curiously, on the machine where I develop it, it works correctly, but on the second machine where I install it, the problem appears. I corrected it by changing an anchor so it could be detected, managed to make it work, installed it on a third machine, and the problem reappeared, now on a completely different screen.
Is this a recurring issue with UiPath, or am I making a mistake somewhere?

Hey @Matias_Clemente.Arg

Ensure your selectors are flexible enough to handle different environments by using variables or avoiding fixed attributes that may change across machines.

Also ensure machines have similar configurations. Different machine settings such as screen resolution, scaling, or even application versions can cause selector issues.

I don’t believe that’s the case, as it involves the same data, on the same website, using the same browser (Chrome). Unfortunately, I am unable to debug it since my intention was for it to be used by UiPath Assistant.
However, I will heed your advice and continue my research.
I developed a small robot that I intended to distribute through the Assistant on various PCs, but on each PC where I run it, I encounter a distinct selector that is not found.

Hi there,

It’s common in RPA to encounter deployment issues. At this point, the best thing to do is to identify what the problem is. Look at exactly what you changed in the selector when the code was moved from machine 1 to machine 2, and then go through the entire code to make sure your selectors don’t have environment specific attributes, as this will cause failures when the code is moved to a new environment.

1 Like

Hi Matias,

With attended bots it’s tricky because all laptops can be different. Things like resolution, chrome version, applications running in the background and also users trying to use their laptop/pc’s themselves at the same time can all interfere.

For the UIAutomation activities try out several input methods to see which is reliable, like simulate click or chromium API. You could also tweak the Wait for page load, visibility & descriptor targeting methods in the activity properties.

Having a user make input while running can also be a struggle. Consider Activities - Block User Input or Robot - Picture in Picture.

Good luck!

1 Like

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