So difficult to access the exception thrown in the "Throw" activity

I’m using a “Throw” activity.

I’m editing this workflow in my secondary monitor.

When I want to change the contents of the exception being thrown, there is no textfield or whatever in the diagram itself to write such value; just the “Throw” name inside the tiny box of the activity and thats all.

Double-clicking doesn’t work, as it does nothing. Clicking on the “three vertical points” doesn’t bring the option I’m looking for, either.

The only way to change the value is going to the activity properties in the right pane, in my main monitor, which is so annoying.

For god’s sake, please @loginerror and/or whatever member of the staff… FIX THE BROKEN undo/red and copy&paste functionality. This software is barely usable without those basic actions not performing properly and it’s corrupting / ruining my projects at the slightest attempt.

Studio Version?
Dependency Version?

I dont experience chronic issues like you, knowing what versions are affected is important for debugging.

It looks like the rethrow activity, I am sure you checked that though? It would give a validation error unless this was in a catch.

Always last version, as I’m on Community. I’m up to date with the packages, also. It started like by chance, but now we keep like this for specific reasons. This way we can try pre-releases, for instance. But don’t worry; we have the licenses.

Lucky you, @Jon_Smith. My mate works with the “commecial” Studio and she experiences the same “chronic” issues as me. We sit next to each other so I can confirm.

Anyway, this is more of a report on a usability problem.

Yeah, that gives me the ick in a commerical setting cause of how inconsistent it can be. I also like the new versions, but there is a balance. I always go with the latests LTS or one back from it. My stable version right now is 23.4

Lol on the licences, I remember we discussed in the past so wasn’t going to raise it again.
There are a huge number of people breaking the licence agreement in my opinion. I get the impression, based on the wave of people fussing that they turned off classic in community, that they aren’t using it for learning or personal use, instead for commerical purposes and don’t wish to upskill and learn to use the latest features. Not cool. But I digress, thats my own personal pet peeve of people both using the software without legal licences aswell as not wanting to learn stuff released in I think like 2020, instead clinging on to their ancient activities.

My only advice here, is to go back to stable LTS versions.

Hi @Jon_Smith,

As I stated in my previous comment, my workmate, who sits to the left of me, is on the LTS, commercial Studio, and she’s experiencing the same issues. We share the misery. At first she theorized also that some of the problems could be a matter of using the “non paid” version, but now she’s convinced, as me, that it has nothing to do.

This is a public university. We are in good terms with the license, as far as I’m concerned. To be honest, it’s a matter I don’t mind a lot, but more or less we were doing fair with what we had, and now they upgraded to 2 developer licenses. From the 1st moment UiPath said there was no concern about that and it sounded to me like fair use so I don’t mind about it anymore.

We’ve had (and still having) some issues with activities so sometimes we don’t have a choice and need to keep an installation that supports ussing the latest cutting-edge features and/or pre-release verions. But, as I said, for this “cronic” annoyances, it rarely makes a difference. And sometimes some of these bugs luckily have been solved and I have an early access to tha by using the Community version.

By posting so many bug reports on this “Feedback” forum it’s not that I don’t know how to avoid the issues or how to workaround them; I just expect they pay attention and address them, as I believe they use this for that.

I get your frustration, but if it were really as bad as you make it seem these forums would be full of people complaining.

Respectfully, one other person does not make a trend.
I lead a team of RPA developers with over a dozen in the team, across multiple versions and clients and although we do experience plenty of issues, I’ve made quite a few pots on it myself, our ones are not chronic like this and usually related to specific scenarios.

Of course; I understand what you mean.

I also have no idea what the average user of this sofware does. Looks to me that are pretty simple things, like creating a spreadsheet, filling in some cells, or appending lines to a text file.

I didn’t have any previous experience with this sort of “visual programming”, but for me it seems the target audience is people with very little experience in programming and for simple tasks, as when complexity of the task gets further than very simply, managing long workflows becomes very difficult. Searching, debugging and other typical programming tasks become very difficult to accomplish here.

I’m not saying what we are trying to accomplish in my organization is that complex, but probably what we want to implement is almost beyond the recommended limits of this tool.

Of course I bet you are experiencing the same bugs I reported here, but maybe you don’t use this tool to such an extent that it’s not a problem for you, or you simply stuck with a workaround (which I have for almost every bug reported here). Me, as I think a paid software should reach a bare minim of basic functionality and quality, I prefer to keep reporting it publicly.

Yeah, and I hope you see I am sympathetic. I know we butted heads before but I think we understand each other.

I still think sharing things like project type, studio version etc help alot when looking at this. Voices get louder if the experience is shared and I am happy to try to see if I also get the error, but I need to know if its worth even trying.

I think things have improved since this thread, at least when I tested now on the latest System and Studio 24.10.6:

It looks like some undo and redo improvements have also made it into the property boxes: