Hello all. I have tried adding the window resolution to match the laptop I am using when building out the test cases to the bot. For some reason the test cases that are ran continues to throw an error about UI element not found and I am unsure why manually there is no problem but fails when I try running it on Orchestrator.
Anyone has any advice on things I should check that could be causing the test to fail with the bot vs manual?
Thank you
Welcome to the community
Are you using hardware events?how are you running in complete unattended?
cheers
@juniorpath If you can, try opening the test server while the bot is running and verify if element/layouts are the same; or take a look screenshot.
If it’s possible, Open UiExplorer in the test server and validate your selector/descriptor.
-Use reliable attributes / casesensitive:propertyName=False / dynamic values *
-Increase timeout of your check app state activity
-Explore inputs methods
simlae type uipath - Search
Hello @Anil_G
I apologize on my late reply and thank you for responding.
I am still new and may not understand but when I am running it I am going to
Testing > Test Cases > Select to run one > Selecting Account & Machine
Does this answer your question?
Sorry if I did not in advance.
Hello @Eric_Alvarado
Thank you for responding and I apologize on my end for my late reply.
I did try to be in the server while the bot is running but it seems like only 1 account can be active in the server at a time. If I am in the server the bot will automatically fail and tell me someone is there.
How would I take a full screen shot approach mentioned?
Thank you for the help.
Hi @juniorpath
-You can try opening the server and start the job from UiPath assistance instead of Orchestrator.
-There’s a Take screenshot activity; you can save the file in a folder. If you’re using the UiPath’s framework a screenshot is taken in SetTransactionStats.xaml for S.E
-Check if the company has the ‘Open live stream/Open recording’ functions available when a job is running
Cheers
@Anil_G I just checked and do see UiPath.Service.Host in Task Manager.
What do you mean by simulate input method? The test cases do pass when ran locally (manually).
As per error looks like may be element is not foundbecause it is there out of screensbound for a click or anything
So simulate input method is a property which will work event if not in screenbounds…like on a element which is there after a scroll etc
In unattended due to resolution differences this might happen as well…in robot settings in orcheatrator → tenant → manage access → robot settings you have the option to set resolution
Cheers
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
