Hi Guys,
I am facing selector issue while running bot from orchastrator in unattended mode, but same bot is running fine when i run it from studio.
Please tell me how to handle such things.
What are you trying to do ?
my bot is unattended on one VM production, there it getting error as selector not found, but same bot when i run through studio to check selector it run successfully.
hi amruta_pawar,
which application are u automating , which environment either test or prod.
Thank you
it is on prod
can you check the selector in prod environment.
@amruta_pawar - pls check the application load time and check the selector timeout in your workflows… maybe applications is responding slow in VM and the robot unable to find the elements in the specified timeout window.
Are you getting timeout exceptions?if yes - pls try below
you can add elementexists or onelementappear activities → based on the activity response → you can perform your actions…
if no - pls share the exception details with us…
I have a similar issue, whereby the selector exists and works perfectly when running from studio (same environment and user) but when running unattended it cannot be found.
Initially the error was "cannot find [contactitem], closest match is unknownitem [50%].
Changing the selector to item changed this error to simply selector not found. The screenshot taken at point of error shows the application exactly how it should be.
I absolutely CANNOT replicate the error in studio. I ran 33 records in studio without error whilst it will fail on the first every time running unattended.
Other activities in the workflow before this point are operating as expected, so why this one is confusing to me.
Anyone have any advice here or any ideas on how to debug this? The selector is fine and stable using studio but can never be found running unattended.
I have the same issue.