2024 年 12 月

2024 年 12 月 17 日

内部版本编号：2025.0.157

New release cadence for cloud customers

We're launching a new cloud-first release vehicle for Studio, Robot, and Assistant that aims to deliver continuous updates with a faster release cadence.

The new UiPathStudioCloud.msi installer is available for users with an Enterprise License and can be downloaded from the Resource Center in UiPath Automation Cloud. You can access the Resource Center by clicking the help button and selecting the Downloads menu option in UiPath Automation Cloud.

关键功能

• 发布周期- 最初每两个月发布一次，目标是每两周发布一次。
• 安装程序- UiPathStudioCloud.msi
• 更新- 每个企业版发布后，UiPath Automation Cloud 中的“资源中心”内将提供最新的Enterprise Edition MSI 安装程序，确保您始终可以访问最新版本。
• Support - Only the latest cloud version is supported.
• Content - The latest cloud version always contains the latest Studio features and fixes.

Benefits of using the latest version of Studio, Robot, and Assistant

• 访问 UiPath 开发的最新更新和创新功能
• 通过机器人和 Studio 部署减少 IT 运营时间和成本
• 降低破坏现有自动化的风险
• Enhanced Robot, Assistant, Studio Web, and Studio interoperability
• 简化了对预览功能的访问，从而减少了手动选择加入的需求

Robot and Studio compatibility

Studio 存储运行项目所需的最低机器人版本，以用于编辑或发布工作流的 Studio 版本表示。 这可确保当前项目只能由相同或更高版本的机器人执行。

在低版本机器人上运行流程将导致显示错误消息。

支持的版本

While Robot aims to deliver the latest features to Enterprise customers in a cloud-like release cycle, the regular release cadence for the Community and Enterprise releases remains the same. This means that the Community version is released every two months, and the Enterprise LTS version is released once per year, following the same versioning.

发布	时间线
社区	每两个月
企业	每两个月更新一次，社区版发布后一周
企业 LTS	每年一次（十月）

About the Robot documentation

To accommodate the new way of releasing Robot features, we have created two new documentation guides:

1. The Robot Release Notes guide outlines the changes included in each Robot Enterprise release.
2. The Robot user guide provides details on the latest additions to Robot.

These new guides complement our existing Robot documentation and are updated with every release cycle.

错误修复

• 有时，执行作业会失败，并显示“无法访问已关闭的管道”或“连接已关闭”异常。现在不会再发生此行为。

• On rare occasions, using the HTTP Request activity in a Legacy project caused the executor to crash unexpectedly with the error: "System.Exception: Could not retrieve the result of the job execution. This might be because a message was too large to process." The error appeared in Orchestrator for failed jobs.

• In coded workflows, an exception might occur when invoking a workflow multiple times in parallel. This was caused by the use of the RunWorkflowAsync method.