When using Long Running Workflow files trying to move or even selecting the arrows freezes the studio program, as you might imagine working with long workflows is impossible due to this.
I’ve seen similar performance issues with large/long workflows where the Designer becomes unresponsive when selecting or moving activities/connections.
A few things I would suggest checking:
Try collapsing large sequences/containers before navigating or moving activities.
Split the long workflow into smaller workflows and invoke them using Invoke Workflow File where possible.
Check whether the issue still occurs after disabling unnecessary Designer panels/previews.
Try opening a copy of the project and see if the same behavior occurs with a smaller section of the workflow. This can help determine whether it is related to workflow size/complexity.
Since you’re on Studio 2026.0.202 STS, also check whether the same project behaves differently on the latest available Studio build.
If the issue is consistently reproducible, sharing the approximate number of activities/nodes and whether it happens only with Long Running Workflow files would help narrow down whether this is a Designer performance issue or something specific to the workflow.
Reopen Studio and go to Home → Settings → General → Reset Settings. This resets Studio layout/design settings.
Restart Studio and open the Long Running Workflow again.
Set the Designer zoom back to 100% and check whether selecting or moving the connectors still freezes Studio.
If it still freezes, create a new Long Running Workflow with only 2–3 activities and connect them.
If the same issue occurs in the new workflow, test the project with the previous/Stable Studio version.
If the previous version works correctly, report it to UiPath Support with the 2026.0.202 STS version, sample workflow, reproduction steps and Studio logs.
This will help confirm whether the problem is with the workflow itself or the current Studio build.
I suggest you ignore the other replies, they are AI generated garbge.
I just tested in Studio 2026.0.202 STS and get the exact same behaviour so its for sure a nasty bug.
I’ll get it escalated asap to the Studio team via the MVP channels as thats pretty severe.
Edit:
Studio team are aware. They say they will fix in the next release.