List of shameful bugs ongoing for years

I’m providing this thread for your amusement. I’m compiling a list of shameful bugs in Studio, most of them widely reported in this forum from long ago, with support tickets reported to the “customer support”, and never addressed, while they spend their time changing the color of the UI (and introducing new bugs in the process).

Feel free to add yours to the list!

  1. Unable to pass dictionary as a parameter for a workflow.

You try to set a dictionary as an input parameter, and then when you try to fill in the value, another dialog pops up, asking you to provide the “keys” and “values”.

See the attached zipped video to see it in action.

There’s a workaround, like choosing another type for the variable (a simple one), then changing back to dictionary. So, for they, this is “enough” to keep it like that for years.

Look at the AI suggestion for the workaround also; it’s hilarious:

Support ticket: #:02888186

Edit: and #:02733377, back in November 2025. You know what the reply by Neerati Akshitha was?

The generic one.

"To better assist you and fully understand the use case and scenario, could you please attach a short voice-over screen recording?
Since the behavior is a bit difficult to interpret through text alone, a video showing:

What you are trying to achieve

The exact steps you are performing

Where the issue appears

What you expect vs. what actually happens

…will help us replicate the issue accurately on our end.

Additionally, if possible, please share a sample project that demonstrates the problem (with any sensitive data removed). This will allow us to review the workflow setup and identify whether the behavior is expected, a configuration limitation, or a potential bug.

We appreciate your cooperation—these details will help us provide you with the most accurate guidance."

Seriously: is it that REALLY difficult to understand what’s happening from the description?? Have they even TRIED to reproduce it??

Unable to pass dict parameter 2026-05-12 123524.zip (7.5 MB)

  1. Clickable column names for the workflow arguments that do nothing

The column names are clicable, but they won’t do anything, like sorting the list by name.

If so, why you make them clickable?

See the attached zipped video to see it in action.

Support ticket: #:02888190

Clickable argument columns 2026-05-08 142945.zip (3.5 MB)

Create HTML Content activity. Using a datatable in it. But taking the first value of de dt instead of the headers for header.

  1. Weird behavior when double clicking on found references

You search for a reference like a variable in Studio. In the results list, you double click on the occurrences to go to the place in your workflows when it has been found and open it. Then in many cases it will just open a grey window title bar.

By the way, inside some workflow areas like try..catch blocks, ifs or loops, whatever activity you have there it will appear like that.

See the attached zipped video to see it in action.

Support ticket: #:02888195

Weird behavior double click on reference 2026-05-01 181018.zip (7.4 MB)

  1. Unable to add activities after an existing one inside an If..Then block

You have an “If” activity. You put an activity inside the “Then” block.

Then you want to add another one after it inside the same “Then” block. You simply can’t.

If you start messing and moving things around, like dragging it out of the activity, then adding attaching the second activity, then putting it back inside the “Then”, finally it will accept it.

This is so clumsy, and it’s shameful that you have to rely on such “workarounds” to simply use one of the most common activities in programming - an “If”.

I’d say it happens inside other similar activities, like Try..Catch blocks, and I’d say this didn’t happen before the UI change, but I can assure it right now.

Cannot attach a video to see it in action because it’s too big.

Support ticket: #:02888200

  1. Random variable type errors in Assign activities

Studio will often and randomly complain about variable type issues in Assign activities, although nothing is wrong. Eventually, by messing around, deleting the variable name inside the textinput and/or writing the name again will maybe “fix” it.

Watch the attached zipped video to see it in action.

Support ticket: #:02888213

Random assign variable types 2026-04-30 092339.zip (9.4 MB)

5.5 Unable to add further activities after a single one inside a Try..Catch activity “Try” block

I found the variation of bug #5 (#:02888213) but this time inside a Try Catch.

I can’t believe that they release a product without noticing such a bug.

Unable to attach a zipped video to see it in action because it’s too big.

Add in the email conversation of the support ticket #:02888200

  1. “Analyze File”/“Project” unable to find runtime errors

You use the “Analyze File”/“Analyze project” functionality.

It doesn’t find any error.

Then you run the project, it throws an error.

It there are errors happening at runtime, then the “analyzer” should be able to maybe run the project to find these ones, there offer advice on fixing them. Or, at least, to be able to show a potential issue there.

Because of this you can spend ages to find what’s causing an error than in the ends turns out to be a very simple one.

Cannot attach a video to see it in action because it’s too big.

Support ticket: #:02888226

  1. Activities inside a “Catch” block appear as only one grey bar

The activities you put there will randomly appear as only a single “minimized” window bar that you can’t expand, you can’t see the card’s values or anything.

The only way to bring them back is, maybe, messing around with the activity. Cutting it, taking it outside, then bringing it back again. Then maybe it will show up “normally”. Until, for whatever unknown reason, next time will display broken again.

Watch the attached zipped video to see it in action.

Support ticket: #:02888239

Grey bar inside catch 2026-04-20 172013.zip (5.1 MB)

  1. Parallel For Each: writing something inside the “Foreach” textinput makes it disappear

Struggled to get this activity working; after days spending time with it it turned out to be totally unreliable. My bet is that no one is using this at all and the company probably doesn’t even know how it “works”, in case it does. There’s no documentation whatsoever (there’s an “official” documentation page, but it doesn’t add anything further to the obvious description of the fields in the activity). No info about the level of “parallelization”, anything.

When you try to put whatever content inside the necessary “Foreach” textinput and press Enter, it will just disappear.

Eventually, randomly, after the 89235798235 attempt, or another day, the value will stay inside the box.

Watch the attached zipped video to see it in action.

Support ticket: #:02818238; closed without any resolution.
Parallel for each 2026-03-04 121627.zip (4.4 MB)

  1. Unable to open contents of “set value” textinput of Assign activity in editor

Sometimes the contents themselves confuse Studio so you cannot open a long value in the editor to change them.

Watch the attached zipped video to see it in action.

Support ticket: #:02888252

Uable to open Assign value in editor 2026-03-02 115552.zip (8.5 MB)

@Bogdan_Sultana reacting with the :robot: emoji cause he doesn’t like getting called out.

This one is a classic. My team has a library activity for transforming DataTables due to this bug.

The only issue on this list I’ve ever encountered is the one where you can only put one activity inside an If/Then. This happens when you’ve upgraded the UiPath.System.Activities dependency, and all you have to do is drop in a new If activity and then it works normally.

For all the rest of these, what version of Studio are you using? Are you extracting from the .nupkg of published processes? Do you have the .runtime versions of dependencies installed rather than the activities version?

Oh here we go again, some of these are so laughably trivial and are not bugs. I expect if you haven’t changed you will demand that they are and that the design choices and intended way things work is just bugs cause you refuse to accept you might just be doing it wrong.

Just on the first one alone. Its not a bug. Lots of data types have rich editors now available, and if you select the braces you get the special editor, if you click the plus you get the normal one where you can write a classic .NET expression.
Its not a bug, this is intended behaviour.

The stuff with IFs and Try Catches I wouldnt qualify as a bug either.
What they did is clean up the Ui so the sequences inside the try catch or IF were now basically embedded. If you had old workflows, where you tried to emulate this tidier look, by already removing the sequence so just a single activity was in, then you get the weird behaviour, just like before, you cannot add multiple items to an If or an else, you have to have a sequence for them to sit in. Difference is the sequence is hidden.

Its not a bug cause they are fixing something that clearly bothered you and it only affects workflows ported over that had their sequences removed.

Everything you complain about is superficial or trival, or caused by you using old workflows and not migrating them properly, or not updating with the new versions.

Hi @pere , thanks for putting this thread together, and for the level of detail in your reports - the videos and support ticket numbers in particular make it much easier for us to trace each item internally.

I’m going to investigate them one by one alongside support and engineering and follow up on this thread once I have more details.

Thanks again for the detailed explanation.

Raluca

Not really fair to say the If/Try Catch thing isn’t a bug when you describe it yourself as “weird behavior.”

A lot of real production UiPath projects are old workflows. “Migrating them properly” sounds simple, but in practice that can mean rebuilding chunks of a project just to restore behavior that used to work.

I agree some of the complaints are more superficial, but I wouldn’t downplay issues that affect existing workflows. Backward compatibility matters, especially in RPA where old long running production processes are common. A UI cleanup causing broken or unexpected behavior in existing projects is still worth calling out.

Also, I sorta agree with user that some of these bugs should have been resolved by now. Take the HTML content from UiPath.Mail.Activities for example, for the past 3-4 years it has never included the header table when importing a datatable. That may sound trivial on its own, but it has meant years of workarounds for something that should probably just work.

I like that in low-code/XAML files they have never figured out how to handle methods with optional arguments. If you’re new to UiPath/C#, this bug can happen at seemingly random times. Just one of those issues you have to know about and chronically work around.

Fair enough, the difference is the complaints here are made in bad faith in my opinion based on this guys history on the forums.
He seems to really hate using UiPath and calls anything he doesn’t like a bug, seemingly trying to weaponize the term.

Had you posted it as a bug, I would have reacted differently as I do not feel you would be doing so maliciously.

I would say the thing I take away from this is support tickets are indeed chronically slow to get resolved or get quality answers, but again I wonder how difficult he is to every solve one to his satisfaction. I find loud, angry voices like this distract from real criticism. I dont want Raluca wasting time looking at these superficial issues, but rather working on the genuine improvements shes been delivering.