I’m encountering an issue with the click activity on a particular element in the process that was developed a while back in Windows - Legacy mode. However, when I create a new process in Windows Mode and perform the same click action on the same element, it works as expected.
Your assistance in resolving this issue would be greatly appreciated.
Hellow @Jahangir_Mohammad
The Best Solution
Recreate the click activity using Modern UI Automation in a new Windows-compatible process, then copy the working selector and input settings back into your Legacy process.
Steps:
In the Windows process (where it works):
Open UI Explorer for the Click activity.
Copy the reliable selector and note the input method (e.g., SimulateClick).
Open the Windows - Legacy process:
Use Modern Click activity (enable Modern Experience in Project Settings if needed).
Paste the working selector.
Set the same input method.
Test the click.
This ensures you’re using the most compatible selector and settings from the working version.
The issue may be due to compatibility differences between Windows - Legacy and Windows mode. Try recreating the activity or selector in the new Windows mode project, as it uses updated libraries and better support for modern UI frameworks.
If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath
I was able to resolve the issue by upgrading the existing packages(UiAutomation and System), which had older versions. After the upgrade, I noticed that a few activities weren’t functioning as expected, so I added timeouts and delays to ensure proper execution.