i have to click on cancel button on a restore popup … in my local its working fin e but in server its creating issue . what should i do to rectify it . i m using click activity for this
Use classic Click activity to click on the Cancel button. Also configure Continue on error to true or check the checkbox so if there is no restore popup, it will not throw any error.
Hi @Pooja_Kanwar ,
try using the image activities, First check the popup appear or not use the Image Exists activity ,pop appear then use the click image activity
Regards,
Gowtham K
First you can try to take a screenshot activity to see why it fails on the other machine. And after that, you try the solutions below if you can use Studio on the other machine:
-
Adjust Selector Attributes:
-
Ensure that the selector used for the Click activity is stable and can work in different environments (local vs. server). Check if there are any dynamic attributes (like
idxoraaname) that may vary on the server. Use Ui Explorer to refine the selector. -
Add a Delay Before the Click:
-
Sometimes, the popup may take longer to appear on the server than it does locally. Insert a Delay activity (e.g., 1-2 seconds) before the Click activity to ensure the popup is fully loaded.
-
Use WaitForReady Property:
-
In the Click activity properties, set WaitForReady to Complete. This ensures that UiPath waits for the popup and its elements to be fully loaded before attempting the click.
-
Use an Anchor Base Activity:
-
If the Click activity alone isn’t working, try using an Anchor Base activity with a reliable anchor element near the cancel button. This can improve accuracy if the popup layout is slightly different on the server.
-
Try Simulate Click or SendWindowMessages:
-
Enable SimulateClick or SendWindowMessages in the Click activity’s properties. These options allow the robot to perform the click in the background, which can sometimes work better in different environments.
-
Check Resolution and Screen Settings:
-
If the server runs in a different resolution or screen settings, it might affect the UI element’s position. In Orchestrator, you can configure the Resolution and Depth under Robot Settings to match your local environment.
-
Ensure the Server Session is Active:
-
If you’re running this on an unattended robot, make sure the session is active. A locked screen can cause the click to fail, especially if the activity relies on visible UI elements.
Regards,
Kardelen
Hi
When I faced the same issue using classic click activity in try catch resolved it
This is the selector