Issue with UiPath Studio 2025.0.157 Community Release

Feedback Studio
, ,
1

@UiPath_Community UiPath studio

Description of the Problem:
After updating to the UiPath Studio 2025.0.157 community release, I’ve encountered significant issues specifically with Switch conditions:

  1. Unable to create variables in the given scope: This issue arises prominently when working within Switch conditions, making it impossible to define variables as needed.
    Even after selecting an activity, it still prompts to select an activity to create a variable.

PFB the screenshot for reference:

The screenshot shows an error message "Create Variable Error: Object reference not set to an instance of an object" in a UiPath automation workflow with a highlighted instruction to "Select an activity to set variable scope." (Captioned by AI)
The screenshot shows an error message "Create Variable Error: Object reference not set to an instance of an object" in a UiPath automation workflow with a highlighted instruction to "Select an activity to set variable scope." (Captioned by AI)1615×688 141 KB

  1. Workflows disappearing post-development: Some workflows, especially those involving complex Switch conditions, vanish after development, creating challenges in implementing new logic.

Steps Taken So Far:

  • Re-installed UiPath Studio: Did not resolve the issue.
  • Tried dragging and dropping new activities: The issue persists.
  • Creating a new Process.xaml file: Yet to try this approach.
  • Re-creating the entire bot: Not fully confident this will solve the problem.

Request for Support:
Has anyone else encountered similar issues with Switch conditions in this release? If so, could you share any workarounds or solutions?

@uipath Looking forward to resolve it soon.

Thank you for your support in advance!

3 Likes
5

Hi @Biswajeet_kumar. Happy new year! :tada:
Thank you for reporting the issues! :pray: We’ve managed to reproduce the first behavior mentioned internally and raised a ticket for it. Hopefully it will be fixed as soon as possible.

Regarding the second behavior, could you please let us know if your project is maybe under any source control, such as Git? Is the vanishing part visible for the entire xaml file? meaning it is deleted entirely from disk? Or does it refer to only a part of the xaml file vanishing - such as the a Switch activity case?
Thank you very much in advance!