HAHA…people who haven’t worked with power automate would never be able be appreciate the beauty and power of UiPath..
to all those who dislike/hate/trying hard to hate UiPath, please work on Power Automate/PowerApps for a couple of months and come back..
Power Automate? Huh?
Wrong assumption!
But dude, this is UiPath forum! Gotta get your sight checked… 
lol.. it’s a pity that your English Comprehension skills are bare minimal and can’t understand a simple comment. what else do you do apart from unnecessary rage bait posts..?
sweety, get a life!
“English Comprehension skills”? Huh?
Sorry dude, you got it wrong again… This is UiPath forum, not DIY-psychology or English grammar forum… But now that you say it,
- Phrases start with a capital letter.
- The same after period.
- Ellipsis consist always of a set of three dots (…).
Rather off-topic and bad manners, though! What a shame!
Let’s please stay constructive, everyone.
We appreciate the feedback, and we will most definitely take it seriously. We also appreciate healthy amount of discussion about the feedback, because it adds context and flavour to how others look at it. In fact, go wild and add to the list if you can.
Keep the feedback coming, and please don’t argue off the topic.
Yeah, and I guess they have a separate activity list to handle the split and merge of strings.
That was one example. There are still countless methods you might invoke in low-code that have optional arguments.
It can feel weirdly inconsistent too because the example you cite only occurs in C# and not Visual Basic.
I think considering you can just press ‘fix’ these days to solve it, I wouldnt class it as a ‘shameful bug’ but rather a small annoyance, but I get why it bothers you.
Hey, just dropping some context on that issue in particular.
In Studio, at design time, C# expressions are compiled using Roslyn Expression Trees. Unfortunately, that specific limitation comes from Roslyn and there have been requests going back more than 10 years for Expression Trees to receive support for modern C# features. For instance: Proposal: extend the set of things allowed in expression trees · dotnet/csharplang · Discussion #9362 · GitHub or Expression tree should support optional parameters · Issue #28481 · dotnet/roslyn · GitHub
Considering that the Studio side fix for this issue would involve a pretty big rework of design-time compilation, it has not yet been prioritized.
I think the developers just need to add an error message for this issue that gives some context. Some sort of “UiPath projects do not support…” rather than leaving the raw error message there. Because without additional context on the structure of Studio, the error does not make sense.
I like Studio Desktop for UiPath stuff, and I like how much C# support has been expanded with coded workflows. This is just one of those issues that has persisted for so long I’m surprised it has never been acknowledged in the error handling.
- Blank content inside tabs
This is one of my favorites.
Every now and then (more often than I’d like to) the content (workflows, activities, everything) disappears; there’s just a blank background.
Very confusing, as one at first things their work has been erased, lost, whatever.
Took me months to realize that the content was still there; it was just that it wasn’t being shown. Then you click on another tab, click again on the previous one and… voilà! Magically the content is back.
Reported countless times via support ticket; the staff always dismiss it as “we cannot reproduce it”. My coworker who sits next to me experiences this very often also, and she has a different computer. Quite unbelievable that they cannot reproduce it.
See the attached zipped video to see it in action.
Support ticket: #:02894203
Tab content disappears 2026-05-21 101753.zip (5.8 MB)
EDIT:
It’s not only the main tab that gets blank; it happens with other tabs, like the variable list. I was able to catch it in action the other day:
This is the typical thing that goes “unnoticed” for months because you think you hallucinated it but you notice “something weird” is going on…
- “Current item” variable inside loop activities not shown on the list and unable to infer its type
Inside a loop activity (“For [whatever]”), there’s a field for the “current item” in the current iteration.
Usually it’s called by default like “CurrentItem” or so. That name can be changed.
The variable, though, is not shown in the Data Manager variable list. You cannot “create” it with CTRL+k inside the text input when writing its name.
Apart from being an inconsistency with the expected UI behavior, it has the effect of making the type of the variable so hard to infer. And that’s necessary many times. Consider the simplest case: you want to move the processing done inside the loop to its own workflow because it’s quite long/complex. You need to pass the “CurrentItem” to the workflow as an input parameter to process it there. Defining it could be a nightmare as there’s no straightforward way to determine what the type of the variable is.
For example, in a For Each Row in a DataTable activity. The type is “System.Data.DataRow”. Only got this after many trials&errors. Next time I have to do it I’ll have already forgot it for sure, and I’ll have to browse between a myriad of similar-sounding names until I find the right one again.
As a minimum, as every other variable in the project, we should be able to “see” it in the list of variables. If it shouldn’t be allowed to modify it as with other variables as it’s “activity dependent”, at least show it in “read only” mode, but at least let us “know” it’s there and see its type.
Sometimes there’s a hint when you hover over the text input for the “CurrentItem”. Nevertheless, although it says “Type:”, this info is not actually the variable type, and it’s inconsistent amongst different “For Each” activities:
Support ticket #:02894251
Yeah… that for each thing… That is actually as it is supposed to.
If you have a bag of candies, the for each item in the bag, implies item is of type candy. It cannot be anything else so there is no need to create it. This goes for any form of collection., that currentitem always if of the type of the members in the collection.
Always wanted to say this: it’s not a bug, it’s a feature 
And for this is is yet again PICNIC issues and the user not knowing how to do things well / skill issues being falsely reported as bugs or support issues.
You can always easily find the data type of the thing you are iterating over. Just press ctrl+space to see all the variables in scope and check the data type, this is not something absurd to do cause you need to routinely do this for any complex objects if you arent the most basic user, for example, what data type is the SpecificContent on a QueueItem as a very trivial example, it also doesnt appear in the data manager tab, but you can see it just as easily as I demonstrate using intellisense and the code editor, as intended in any .NET thing.
For each is even easier as you can also control the local variable name and change the data type.
Its also not a ‘bug’ but a core way that the Workflow Foundation code that UiPath is built upon (originally made by Microsoft) that certain activities have what are called local variables and you cannot delete them.
If these are the support tickets being made then I see why they don’t get solved. There is nothing to solve, it a matter of needing to learn how to code with .NET etc.
Disagree; I already explained it on my previous message.
“DataTable” type is not the same as “bag of DataRow”. So it’s not that straightforward and that’s why it’s such a pity to find out.
If for you it’s always so trivial to find it by looking at the docs, doing some sometimes “obscure” inference, trial&error, and so, good for you. I prefer to see the variable, in readonly mode if necessary, in the list of variables, as with any other variable in the workflow, and see the type there. The list is a helper, also, to easily locate the name of the variables (for instance if you need to reference it and you barely remember its name, like the very first letters), and there shouldn’t be an exception so in these loops you have to go and look for the name of the variable… at the beginning of the loop, instead.
Another top ten one. Probably the best of them all.
Customer portal interface breaks any attached image on UiPath’s message replies, so ATTACHED IMAGES ARE NOT VISIBLE.
I have been begging to them for 3 years to fix this once and for all. NO SUCCESS. I’ve been making them note how shameful and embarrassing is that their “customer support” tool is broken itself. THEY HAVEN’T BEEN ABLE TO FIX SUCH A SILLY, SIMPLE BUG IN 3 YEARS.
They include screenshots in their replies. THEY ARE NOT VISIBLE. Instructions to sort out issues can’t be followed.
What else can be said