I’ve recently converted my UiPath project from Windows Legacy to Windows (my machine is Windows 10, 64bit).
Soon after, the project became very slow and resources demanding.
Every simple action I make (opening a workflow, scrolling, editing, running etc.) is resulting in a very slow reaction and also affects other process on my pc, due to the UiPath high load.
When I run the project, it runs a validation and a compilation, which together may take about 5-10 minutes (depending on the amount of changes made to the project).
Attached are some screenshots.
We are aware that our latest release has some performance issues that got exposed lately and we will address some of them in the next path 22.10.4 and during the next releases.
Thank you.
Do these issues result from the conversion from Legacy to Windows, or are they exist in the Windows version anyway?
(I’ve considered to recreate a copy of my whole project in a new automation, assuming the first assumption).
If updating to 22.10.4 doesn’t help with the performance issues, what are the next steps?
The current version is really bugged, keeps stalling or even worse not responding and ending up chrashing Studio.
It’s really really annoyoing to work with and makes it almost impossible to do any work in the latest version
Yes, it’s just impossible to work like that. Is there an alternative? is there another automation tool which can import an existing UiPath automation, so I don’t have to create it again?
Has anyone found a workable solution to these issues? Studio has become a pain to work in. The switch to Windows from Windows legacy has been the worst transition ever…
The 22.10.4 version doesn’t solve it. Its extremely sluggish to respond to basic actions in simple workflows in a Windows compatibility. This needs urgently fixed.
I am facing the same issue. Its the worst version I have seen in last 5 years. Development cycle is taking too long. Particularly Ui automation. Also, there are lots of functionality which are missing (for example: for-each loop doesn’t provide option to select the variable type). Scary if this is going to be the trend. I guess this release shouldn’t have been release as a LTS release.
Since this is an LTS release, shouldn’t this be fixed in this release itself? Why the fix is being planned for next release? What happens to people who have upgraded and now stuck with this version?
Thats completely unrelated to the Studio version, that all depends on what activity package you use and they don’t follow the same LTS cycle as far as I know.
As for Studio, I believe this is fixed now and Windows projects work fine. I do personally feel like VB.NET works slower that C# but I cannot say that for sure right now.
Sorry, can you please be more specific?
Team is using latest 2022 studio version and it takes 15 min for solution to compile and run.
Do we need to upgrade packages to latest of 2022 version as well for this to be resolved?
Which patch?
It might be that you are on a minor version before they fixed this, if you are on the latest 22.10 patch then maybe its related to your project, 15 minutes indeed is insanely long so something isnt right.
Anil_G
ashokkarale
prashant1603765
sonaliaggarwal47
Juan_Pablo_Ortiz
yedukondaluaregala
Rahul_Rajendran
sharazkm32
gorby
V_Roboto_V