For the same selector, bot is working fine in development machine and failing in UAT machine

I have developed a code on one of my server machine and trying to execute same code on physical laptop but it is failing, some activites are working and some are not working.
Resolutions are same for both machine

Hey @Pratik_Gangane
It’s hard to say what the issue might be without more details. The cause could be permissions differences, robot configuration or even a missing application. Could you please share the exact error message and specify which activities are not working?

Mostly click activities are not working, Error is bot is not able to identify the emelents even the elements are present on the screen. Could you please tell me more about what permissions you are asking about?

@Pratik_Gangane
I’d suggest checking:
– if the selector for the activity is exactly the same on the server and the laptop,
– whether the application behaves differently on the laptop (e.g., window title, app version, screen resolution),
– trying a fuzzy selector or anchor if the element is tricky to capture.

If possible, please share a screenshot of the selector that’s failing.

Hi @Pratik_Gangane

Use SimulateClick or SendWindowMessages instead of default click for better reliability. Confirm that display resolution and scaling are set to 100% on both machines. Check if the selectors are valid on the laptop using UI Explorer as elements might render differently. Make sure the robot is not running in a locked or minimized session unless properly configured.

If you found helpful, feel free to tick as a solution tick.
Happy Automation

@Pratik_Gangane,

Use Ui Explorer on UAT machine and check if the selectors are really the same. You can get standalone Ui Explorer exe from Orchestrator → Downloads.

Hi @Pratik_Gangane,

Please confirm below:

  1. if the environment for the application you are using is same on both machines?
  2. how are you running the process in both machines? Unattended? Or via studio/assistant?
  3. Please use Uiexplorer to explore the selectors of failing click activity in both machines.
  4. It can be the case that selectors are different for different application environments and if that is not the case, try to run the process the same way you are running it in the machine where it is working properly.
  5. Enable send window messages property of click activity or simulate click property and test.

Hope this helps.

Regards
Sonali

What you mean by environment, will you explain in bit detail?
I’m running process through studio.

There’s high possibility that selectors might have been changed in UAT.

What you can do:

  1. Open Selector window of Particular Ui Activities and click on validate.
  2. If Its validated then click highlight where you will see if bot is able to identify actual element on the application or not.
  3. If highlight option not highlighting the actual element on application then you need re-map selectors again.
  4. If highlights option working then change its method such as Simulate, Send Windows message, and Hardware
  5. If you are using modern Activities then you can also try as Chromium API as your input method.

Thanks!!

Hi @Pratik_Gangane please use dynamic selectors example : if you are pulling some data or selecting data in the the form of loop their you can use variables or arguments, it will help in selectors select your respective ui element without any issues