Issue with Flow Decision in UiPath Studio: Error When Using Only False Condition

[Eduardo_Mazzochi]

Hello everyone,

I’ve encountered an issue with the Flow Decision in the latest version of UiPath Studio, which is causing errors when I try to use only the false condition. Here are the details:

UiPath Studio Version: 24.10.0-beta.17118

How to Reproduce the Bug:

1. Create a Flow Decision.
2. Use a simple condition, for example: 1 = 2.
3. Configure the flow to follow only the false condition. Do not use or define the true condition.

Problem Description:

• In previous versions of UiPath Studio, the false condition would exit to the left and the true condition would exit to the right. This setup allowed me to work exclusively with the false condition/flow without issues.
• In the current version, if I try to work only with the false flow and do not define or use the true flow, the following issues occur:
  • The Flow Decision node throws an error, specifically: Object reference not set to an instance of an object.
  • The flowchart fails to load or becomes unresponsive.
  • The logic for the Flow Decision does not follow the standard left-for-false and right-for-true pattern.
  • I am forced to define a true flow even if I do not need it for my workflow, disrupting my intended process and design.

Error Message:

Object reference not set to an instance of an object.

Steps Taken and Observations:

• After further testing, I observed that the issue arises when I do not set up the true condition, even if my workflow only requires handling the false path.
• This change in behavior is preventing me from using the Flow Decision as I did before, where I could handle only the false conditions efficiently.

Additional Notes:

• The requirement to define the true flow first is new and was not present in the previous version.
• This is causing significant disruptions in my workflows where the logic depends solely on the false condition.

Has anyone else encountered this issue or found a workaround? Any insights or solutions would be greatly appreciated!

This is generating an error when opening my projects that only use the False flow. Generating the reported error and preventing me from adjusting the project. The only way is to delete all flow decisions

Thank you!

[Raluca_Laic]

Hi @Eduardo_Mazzochi , thank you for flagging this to us. This issue is currently being worked on alongside another reported issue, with a fix being deployed in the next patch.

As a workaround for the time being, you can create a True branch linked to an empty sequence or an equivalent, then reopen the file.

[Eduardo_Mazzochi]

Thank you for your feedback and attention!