After a few days working with new version of 2024.10.1:
The “change tab, you get a grey screen” bug (the one you long promised "will be fixed in next version) is still there. Right after installing the update, during 1st run on the new version, it happened again, and still happens randomly.
“This change cannot be done while debugging. Would you like to keep the changes and stop exectuion?”. While in a debugging session, if the execution has to enter in a certain workflow, it opens it in its own tab and displays it. When Studio does that, then suddenly the file appears as if it was modified, but is not the user’s culprit as he hasn’t done anything as he’s not interacting with it – you’re merely debugging. Studio does something “internally” when opening it and an * (asterisc), indicating that the file is been modified, shows up. Then Studio shows this popup asking you to choose if you want to stop the execution. This makes debugging very, very annoying, almost unusable. Lots of shows up per open workflow, lots of files with an “*”, as modified, even if you didn’t modify (you couldn’t!) anything. Potentially corrupting your project. And potentially ruining your debugging session if you choose the wrong “Yes” or “No” answer after so many questions.
It’s been quite some time I didn’t post on this forum. I switched to opening tickets, hoping it would be more useful when it came to getting bugs fixed or explanations about how to use certain activities lacking proper documentation or not working as stated in there, the docs. Unfortunately, the experience hasn’t been positive either, but obviously far more favorable for the company as their miseries stay hidden to the eyes of the outside world. Now it’s time to post everything back here again. It’s obvious this software hasn’t been properly tested before releasing it, and not only it doesn’t fix the bug that were promised to fix several months or years ago, but also introduces new one.
It’s unexpected to show this message when you are doing a regular debugging. Unless you make changes to the workflow, just opening workflows during execution should not trigger this.
Will try to replicate the same and come up with a fix in an upcoming version if it’s needed.
Maybe it’s related to some specific projects or only to mine.
My mate tried some debugging and didn’t happen to her.
To me it happens all the time. Not only while debugging it automatically makes this “changes” (but there’s no real changes) when stopping on a breakpoint, but also in other project by merely double clicking on a Workflow and opening it.
Looks like I’m cursed with this software. Oh well.
If you can find some steps to replicate the issue (even providing a sample project) would help us in fixing the issue. We have not received this report so far and I was not able to replicate the behavior described.
This issue is happening to me as well and I have never seen this before. To put you in context, I’m trying to work with SAP and when trying to check a box using an if activity the Studio gives me this message.
One thing that I have done during debuggin before the message appeared was to change the target in a Click Image activity but I don’t think any of this relates to the issue that @pere is having right now.
I can’t edit the message but after closing Studio and opening again this issue is not happening. Maybe this helps in the meantime but it’s an annoying solution if I’m being honest.
If I had to guess, I’d suspect integration service stuff being the culprit as that will ‘change’ the workflow just by looking at it as it refreshes the connection etc.
Otherwise it could be other things, I dont have enough experience on 24.10.1 yet but I unfortunately have to agree that its not a very stable release from my experiences so far, I had multiple nasty freezes just writing simple annotations where I had to hard crash studio to reset and even then it wasnt clean as it claimed the project was open elsewhere.
I think it might be releated to the Autopilot stuff, which currently is abit intrusive when writing annotations.
I also think the autopilot for the name of activity is not great as its waaaay too long and should be the annotation.
@pere - have you seen my ask? It’s not going to be fixed by magic.
If you can find some steps to replicate the issue (even providing a sample project) would help us in fixing the issue. We have not received this report so far and I was not able to replicate the behavior described.
Hi,
I’m working with Studio 2024.10.1 and experiencing some issues similar to those mentioned in this post. When I try to debug, the Studio is very slow. It can take several minutes to start debugging. I’ve also encountered the issue where the file changes while debugging.
Additionally when I open the Studio, an extra transparent windows appears.
Sorry for my late reply. I was on vacation in August.
Neither by magic nor by any other means. Since I started working with this software I haven’t seen anything I reported, either here or by customer support ticket, fixed. Maybe some promises of a fix, that remained frozen over months and months and never heard of them again.
PS: the steps to reproduce this are clearly stated here. Just debug a project. You have plenty reports of other users experiencing the same. Maybe you didn’t test it yourself enough.
I can’t comment on the first bug you mentioned, but the constant prompts to keep/discard changes while debugging is frustrating. It’s a great feature in theory, but the way that UiPath modifies XAMLs on the fly nullifies it’s usefulness as you often have no idea what’s changed. Safest thing is just to click ‘No’ for everything. I can’t reproduce it on-demand, but I see it multiple times a day while debugging or running test cases in various projects.
I went to Cloud and downloaded again Studio desktop from there, as the version I see on my existing install is still 24.10.1:
Let me say once again that I find this rather clumsy. It obliges me to download again a 1 GB file, then start the install process again, I get asked again the usual questions as when installing it for the 1st time. I only want to update; I don’t want to remember if the selected options are the proper ones, etc.
Then when the install process finally starts, I get an error:
Then I click on the “View logs” button but nothing happens. If I go to Studio’s logs folder, I see no log related to this (in fact, as I didn’t use Studio today yet, there’s no .log file there with today’s date).
How unlucky we are that the salesman always tells us that no other of your customers is ever facing this sort of problems that we always face, one after another
As your partner company that’s providing support to our organization told us several times to get used to rely on these forums as a source for support, I didn’t have the impression that I was doing anything wrong.
As I was sure that you were aware we are using the Enterprise version and that our organization is paying big money for the licenses, I thought also you had that in mind when giving me the instructions.
Finally, I was told in these forums by some member of the stuff, if I’m not wrong because that was during my very first days as a UiPath’s user, it was a break of the license to be using community versions of this software at the same time as commercial ones.
You reported a bug that I tried to be aware of, replicate the issue and fix it.
The fix is delivered first in Community. And we have done this already. Later this month, we will be releasing the enterprise version that also includes the fix.
I am not saying you did something wrong, I just don’t understand why do you complain that I am not aware that you are not on community. This is a community forum so if you want the latest updates you need to use community.
ashokkarale
Julian_Muhlbauer
SorenB
Jaeyoung_Jung
Jon_Smith
avolaunch
Anil_G
MOMOMOMO
dokumentor
naveen.s