Studio release notes

February 23, 2026​

Improvements​

• More than 250 characters
• The less than (<) and less than or equals (<=) symbols

Bug Fixes​

• Changing the tenant in Studio could fail without a UI indication when Assistant was opened and a job was running or Autopilot for Everyone was enabled.
• Studio became unresponsive when creating a variable from the Plus button on a secondary screen.
• An unexpected "The project has validation errors and cannot be published." error occurred when publishing some projects from the command line if the projects contained coded workflows.
• The value of the Automation Hub URL field was not saved when publishing some projects.
• Closing an editor using the Cancel button or the Esc key could move focus from Studio to the previously used application in some projects.
• The default values for required input arguments set in Studio were ignored when running some processes in Orchestrator.
• An "Unable to cast object of type 'Microsoft.VisualBasic.Activities.VisualBasicValue'1[System.Object]` to type 'System.Activities.Argument'" validation error occurred when setting the default value of an argument of type String in some StudioX projects.
• Studio became unresponsive when adding some activities from the UI Automation package v24.10 or older that used a target indicator.
• Solving Git conflicts in projects that included Excel files could corrupt those files, preventing them from being opened.

February 9, 2026​

Bug Fixes​

• Two additional parameters appeared when consuming a library that contained a Get Newest Email activity when the Email folder option was previously configured in the library.
• Machine resource consumption unexpectedly increased in some projects after upgrading from a previous Studio version.
• Both design and runtime packages were created after publishing some libraries even if the Separate Runtime Dependencies option was disabled.
• You could not assign a value of type System.Object to type System.String in the To property of the Assign activity.