UI element issue attended vs unattended

Hello I use “click” activity in modern design, it seems the only reliable way is to use image capturing (hardware event), it works fine in attended mode but when running unattended it failed to be identified. Please advise what should I try to fix this. Thank you.

Web application or desktop application?

web application, thanks

Did you check “Responsive Website” option ?

1 Like

Thanks I’ll try that!

There’s no reason you should have to use image click in a web app. You just need to get your selectors and input methods correct. Show us your selector.

Hi @Lynn_Song

Image selection is not always seems to be reliable one when dealing with unattended automations .
Please try to use other selection and input methods as mentioned by @postwick .
Also , please check this thread

As you mentioned it is unattended automation for website , please try to use Check app state activity , highlight your selection element in it , in element to appear add Timeout value ( add a higher value in seconds ) .
Give it a try , hope it works for you .
Thanks

There is a possibility that your unattended session is logging in with a different resolution than your current screen when attended, therefore the image might be different, forcing the automation to fail, as image is enabled on the modern selector.

Could you please double-check your unattended robot screen settings in orchestrator?

BR,
Ignasi

Thanks everyone for helping me out, yes it was indeed the selector, part of that requires wildcard to work properly.

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