Process can't find UI element when running Unattended

Help Orchestrator
,
1

I have a process that will run just fine when run on the machine it was developed on, but when I try to run it on a VM unattended, it has trouble finding UI elements.

Two messages I’ve seen:

  • Cannot find the UI element corresponding to this selector
  • Uninitialized UI node

I have tried the following:

  • Using unsimulated clicks and types
  • Changing robot resolution to match my workstation
  • Adding as many attributes to the element selectors as makes sense to specify them

Still no luck running unattended. It will USUALLY work if I log in on the VM and run the job from Orchestrator, but not always. It ALWAYS works when I run the process on my local machine.

Any thoughts out there?

2

Did you accidently publish your process as a background process?
Yes? Change it to a Front-end process and republish.
No? A problem I had in an older setup was that the job started running, but the windows desktop wasn’t fully loaded yet. Try starting your process with the activity ‘find element’ targeting the start button in the taskbar. Apply a proper timeout.

Might not be your solution, but you might just get lucky :wink:

1 Like
3

@GabrielVbs

Is the robot installed in service mode?

Cheers

1 Like
4

Hi @GabrielVbs

UI element selectors can sometimes vary across machines due to dynamic attributes or different application configurations. Review the selectors used in your automation and consider using more robust selector strategies, such as wildcard attributes or relative selectors, to increase their resilience to changes.

Thanks!!!

5

Thanks for the answer bro, but I posted it the right way and made sure windows was ready. Didn’t work, no luck

6

Yes it is :sob:

Cheers

7

@GabrielVbs

Did you happen to sign out properly the user

Also is the login to console set to false while setting the resolution

If there are screenshots can you see if there is any difference

Cheers

8

Compare the selectors from production and development if it’s matching no issues otherwise you need to update the valid selectors from prod to development then publish the package

On the way never forget enable extension in all way

All the best

9

There is one option at studio called framework try to enable one by one and go ahead with your activities that may give you robust selectors