Renaming variables not working

I’ve recently not been able to rename variables from the Variables pane under Data Manager.

The problem is as described: I open the Variables pane, rename the desired variable, and hit Enter. When I check a part of the framework where the variable is referenced, e.g. an Assign activity or a workflow argument, it reverts back to its old name in the Variables pane - as if I never did anything.

Has anyone ever encountered this before? This started happening after I updated some dependencies. Note that the scope of these particular variables are always inside the current workflow I’m working with.

Hi @kristjankarl

Looks like a bug in specific version.

Another user also complained of same. Are you also using UiPath version 2025.0.167 STS?

Hi @sonaliaggarwal47, thanks for the reply!

Yes, I am using that particular version. Hopefully it will be resolved soon.

An update:

After restarting Studio and trying it out again (I am using a REFramework) I found that I was able to rename a variable inside the Process.xaml - I had a Multiple Assign activity at the top of the file where I was able to rename one of the variables.
However, I have other workflows invoked inside of that file, and inside them this still occurs. This applies to Workflows, Sequences, and Flowcharts that are invoked inside it.

1 Like

I’ve had a similar experience myself. Without hesitation, I recommend deleting the variable and creating a new one, rather than trying to rename it.

While that works for variables inside a small scope, the main issue stems from not being able to rename a variable which is referenced throughout the project. If I were to delete such a variable and create another, I still have to go through the project and replace every instance of the old one with the new one.

You can do it! If I am in your position, I will do it if necessary.

Of course I will do it if I have to :slightly_smiling_face:

I am only pointing out a bug in a feature which makes life easier when it comes to developing. This also hasn’t been a problem before! There have been other posts about this and I suspect this will be fixed in a later update.

1 Like