Chrome automation - Browser mode - VDI

[NavaneethanSubr]

We have automated a process in chrome application. Process runs in VDI in unattended mode.
When new element spied and checked in debug mode - VDI is taken through PAM, its highlighting and working.
But when we try to run it from control room in unattended mode. BOT fails to highlight the same element worked in debug mode. What might be the issue. Please let me know if more details required. Thanks in advance.

[PabloSarabia]

Hi @Navaneethan Subramani

Just a suggestion for this. Did you try to run the process unattended but with the VDI window opened?

I have this kind of issues with VM. All the interactions fails if you don't have correctly opened the session like a "human".



Hope this helps you.

See you in the community, bye 🙂

[FrankJelstrup]

Hi Navaneethan,

There can be a lot of reasons for this, most common is that your element is not ready yet. Insert a wait stage to wait for the element before reading/writing to it.

Another common problem is that your VDI uses a different resolution than the desktop you debugged on. You should make an RDP to the VDI, see it run successfully through the control room in unattended mode. If this work, try to run it again after restarting the VDI and not being logged in. IF it fails while you are logged in, something is different on the VDI than on your Test Desktop. IF it succeeds while you are logged in AND fails on running while you don't look(RDP to it), the chances are quite high it's a resolution problem.

Good luck debugging 🙂
Frank