Automation 360 v.37 Release Notes

Release date: 4 June 2025

Review the top features in this release and view other new features and exciting enhancements for Automation 360 v.37 release.

  • ビルド 37468: Automation 360 (クラウド)
  • ビルド 37468: Automation 360 (クラウド-Sandbox)
  • ビルド 37468: Automation 360 (オンプレミス) and IQ Bot (オンプレミス)

We have released the updated クラウド ビルド 37468 (previously Build 37411), クラウド-Sandbox ビルド 37468 (previously Build 37411) and オンプレミス ビルド 37468 (previously Build 37379). For information about the updates, see Release updates.

Highlights of this release

Here are the top features in the v.37 release:

プロセス推論エンジン: Powering differentiated process automation outcomes
The industry’s first プロセス推論エンジン (PRE) is the core capability powering several advanced AI products and enabling us to deliver exceptional experiences to our customers. This engine fuels capabilities such as generative automation, self-healing automation, and advanced document processing, and enables AI エージェント to plan, act, and learn continuously.

With this release, we are augmenting PRE with the relevant and necessary context to enable COEs to accelerate the development of agentic process automation at scale. See, プロセス推論エンジン が Automator AI を強化.

  • Build 3x faster with advanced models: The new planning and reasoning capabilities enable developers to design, build, and configure automations with significantly greater accuracy and completeness. With Co-Pilot for Automators, developers can now automatically apply best practices such as naming conventions, exception and handling, automatically create and configure variables, and write Python, JavaScript, and VB code.

    See プロンプトによるオートメーションの構築.

  • AI ガバナンス : Provides transparency into Co-Pilot for Automators. Administrators can view prompt and event logs, Co-Pilot for Automators responses, and user feedback for each prompt.

    See AI プロンプト ログ.

  • Self-healing automations with vision fallback: 生成レコーダー can now prevent over 60% of automation failures by combining visual and structural insights from live application screens. This makes automations more resilient, adaptive, and enterprise-ready even as business applications evolve. The new vision fallback capability leverages a sophisticated ensemble of AI models to deliver powerful self-healing even in complex, dynamic UIs.

    生成レコーダー - ビジョン フォールバック

注: New planning and reasoning capabilities in Co-Pilot for Automators and AI ガバナンス are available on public クラウド only.

Image showing benefits of enhanced PRE.
Human-agent collaboration: Turning natural language into action with PRE
We are redefining the employee experience in the era of AI エージェント through a new conversational interface powered by Automation Co-Pilot. This innovation combines fragmented knowledge access and workflow execution into a single, unified experience, available standalone or embeddable in any application.

Users can now retrieve accurate, source-attributed information across company systems and documents, and trigger automated processes, simply by using natural language. This results in faster outcomes, fewer manual steps, and a more intuitive way to work.

  • Intent-based automation discovery: Powered by the industry’s first and only PRE, helps users find and launch the right automation instantly while respecting existing role-based access controls.
  • Enterprise-grade security: Safeguards sensitive information and ensures users only see what they are authorized to access, balancing comprehensive information sharing with robust data security.
  • Built-in auditing and governance: Provides full visibility into conversational interactions and automation activity by helping organizations stay compliant with regulatory and internal policies.
注: Human-agent collaboration is part of the Automation Co-Pilot plus license and is only available on public AWS クラウド in North America. We plan to provide support for EMEA customers in an upcoming update.

conversational automation concept

See Automation Co-Pilot による会話型オートメーション.

Process orchestration: Advanced process modeling and real-time execution
We are reimagining how enterprise teams build, manage, and scale agentic process automation. With a modern design experience and streamlined navigation, our new process orchestration engine brings together visual modeling, real-time insights, and advanced orchestration across AI エージェント, Bot, documents, APIs, and teams.
  • Streamlined process modeling and optimization
    • Visually model complex workflows using BPMN with swimlanes.
    • Design modular and reusable logic with support for unlinked nodes.
    • Navigate large-scale processes easily with minimap, pan, and zoom tools.
  • Unified orchestration layer
    • Orchestrate Bot, APIs, documents, and teams within a single, cohesive workflow.
    • Enable event-driven automation using ウェブトリガー, with server-side filters to process only relevant incoming data, reducing system load and boosting performance.
      注:
      • ウェブトリガー are free to use with a Bot Creator license. However, you require an Enterprise Platform license to execute unattended automations.
      • ウェブトリガー are currently available to customers on AWS クラウド only.

      See ウェブトリガー.

Enhanced developer experience
  • Smart navigation breadcrumbs streamline movement between assets and editors.
  • Access the in-app Help Center for instant contextual guidance.
  • Build faster with a wizard-based Expression Builder and improved validation and error handling.

These enhancements provide a solid foundation for process orchestration at scale, empowering teams to move faster with more visibility, accuracy, and control.


Image showing new capabilities of Next_gen Process Composer

See 次世代 Process Composer.

Deploy on any platform, including macOS
This release expands automation capabilities to a growing segment of enterprise macOS users across all deployment models. With comprehensive support for web applications, macOS native applications, and macOS devices, Citizen Developers and enterprise teams can seamlessly build and run both attended and unattended automations, unlocking broader and scalable use cases.
  • Seamless macOS automation development: Citizen Developers and automation professionals can now build automations involving both macOS native and web applications. By accessing the Control Room via Chrome and Safari, Citizen Developers can develop and execute automations directly on their macOS desktops, ensuring a consistent development experience across both macOS and Windows.
  • Web and macOS native application recording : A new macOS-compatible recorder enables developers to capture user interactions in browser-based web applications and native macOS applications. This simplifies the creation of precise, repeatable automation workflows within the macOS environment.
  • Attended and unattended automation support: macOS users can now leverage both attended and unattended automation, allowing for the execution of scheduled tasks and business processes without manual intervention. From nightly data aggregation and report generation to customer follow-ups, processes can run reliably across scalable macOS device pools and WLM queues.

    オートメーションをスケジュールする | デバイス プールの概要

  • Extensible support for macOS native applications: This release further deepens native macOS integration with the addition of key automation パッケージ:
    • iWork suite integration: Automate workflows using Apple Mail, Apple Numbers, and Keynote for tasks such report creation, data entry, and analysis. See Apple Numbers パッケージ.
    • Mail automation: Read, draft, and send emails with attachments. See Apple Mail パッケージ
    • AppleScript support: Power users can embed AppleScript into automations to customize interactions with third-party or legacy applications. See AppleScript パッケージ.

Additionally, developers can use the Package SDK to create custom macOS パッケージ, enabling automation for proprietary, specific, or complex applications and achieving enterprise-grade coverage across the entire macOS ecosystem. See パッケージ SDK v.37 リリース.

注: macOS support will be generally available across public クラウド, private クラウド, and Community Edition.

See macOS サポート v.37 リリース.

Other enhancements
  • Workload management at scale

    Automation leaders can now process multiple queues in parallel across available devices, dramatically improving workload throughput.

    • Faster SLAs through parallelism: With concurrent processing of multiple queues, SLA times are significantly reduced. For example, processing three queues in parallel can reduce overall processing time to roughly one-third of the original.
    • Optimum license and device utilization: Since idle resources are now put to use, you realize much higher license and device utilization, and eventually higher ROI on Automation 360.
    • Simplified ワークロードの管理 : Parallel queue processing works on default devices. Therefore, ワークロードの管理 (WLM) becomes an easy three-step process: Select Automation > Select Queue > Select users.

    Parallel queue processing in WLM

    See 並列キュー処理.

  • Sensitivity label support in Excel automation
    The Excel の高度な操作 パッケージ has been enhanced to support sensitivity labels (managed through the Microsoft Purview compliance portal). You can apply and retrieve the sensitivity label to or from Excel file using the respective Set and Get sensitivity label アクション within the パッケージ. Using sensitivity label, customers can now classify documents such as General, Confidential, and Highly Confidential, and enforce protection policies like encryption and access control. This feature helps customers to perform the following:
    • Ensure Excel documents remain compliant with internal security policies
    • Reduce risk of data breaches and regulatory non-compliance
    • Protect sensitive information by controlling access and applying consistent classification

    See 感度ラベル.

  • Co-run Python scripts across multiple automations with shared session
    The Python スクリプト パッケージ has been enhanced to support global session which can be shared across parent and child automations. Previously, each child automation using a Python スクリプト initiated a new Python session, which led to maintenance overhead and slower performance. With the shared session capability, customers can now perform the following:
    • Avoid duplicate sessions
    • Maintain session continuity across automation boundaries
    • Improve overall performance and efficiency

    See Python スクリプト パッケージ.

  • Grouping by automation run hours: Realize your most valuable automations, devices, and users
    Automation run hours are one of the key metrics to understand the adoption of automation in your enterprise. The Grouping feature in Automation Command Center (ACC) enables you to realize the top automations, devices, and users that contribute to those run hours. This information is critical so that an automation lead can then verify the following:
    • Top devices are maintained in the best of their health with frequent updates.
    • Top users get the best of the resources to continue providing high value.

    Grouping of automation run hours in ACC

    See 自動化ダッシュボード.

Release updates

Date Update
13 August 2025 Build 37468 (クラウド) includes the following:
  • Includes July 2025 package updates. See 2025 年 7 月
  • Introducing AI スキル page which displays AI スキル and AI スキル templates assigned to users. See スキル.
  • Amazon Q with Automation Co-Pilot feature is enhanced to allow users to upload multiple files at once to AI knowledge base for Automation Co-Pilot. See Automation Co-Pilot による会話型オートメーション.
  • Audit log feature is enhanced to allow users to search for audit logs for a maximum of 180 days. See 監査ログ.
  • Fix for an issue where users were not able to promote Bot from public repository by selecting the target URL and API key having angle brackets (< or >) (Service Cloud Case ID: 02221265, 02219560, 02221725, 02223059, 02223813).
  • Fix for an issue where the information on the User group tab on the Edit Process page in ビジネスユーザー向け Automation Co-Pilot kept refreshing when the Control Room language was set to a language other than English and deployment resource was not allocated (Service Cloud Case ID: 02222784).
  • Fix for an issue where automation failed when hidden variables were submitted via Automation Co-Pilot used as an embedded widget. (Service Cloud Case ID: 02222829).
  • Fix for an issue where users were not able to export Automation Co-Pilot tasks when the number of tasks was more (Service Cloud Case ID: 02223778).
  • Fix for an issue where automations failed to download Bot or dependencies when a child Bot using アクション in the 画像認識 パッケージ had scanned or manual dependency with its parent Bot (Service Cloud Case ID: 02220514, 02224111).
  • Fix for an issue where automations failed to download Bot or dependencies when using アクション in the レコーダー パッケージ (Service Cloud Case ID: 02184779).
  • Fix for an issue where users were not able to save changes after editing a schedule and no device pool was selected (Service Cloud Case ID: 02222783, 02224328, 02226718, 02227046).
  • Fix for an issue where automations failed when an アクション was disabled and included an empty or invalid condition (Service Cloud Case ID: 02221856).
  • Fix for an issue where automations continued to execute even after the scheduled Runtime time out value in certain scenarios (Service Cloud Case ID: 02219452).
  • Fix for an issue where users were not able to add or delete Run as users for roles (Service Cloud Case ID: 02224593, 02224668, 02225922, 02226081).
  • Fix for an issue where users were not able to import learning instances with validation feedback that included concurrent request and duplicate service fields (Service Cloud Case ID: 02213769).
  • Fix for an issue where a parent Bot failed to execute due to intermediate dependencies on itself (Service Cloud Case ID: 02215311, 02213762, 02220559, 02222147, 02224082, 02224963).
  • Fix for an issue where the bulk package update failed because actions used in a child Bot was not present in the previous version of the child Bot used in the parent Bot (Service Cloud Case ID: 02207757, 02225626, 02227363).
  • Fix for an issue where checking out a Bot failed when it contained large dependencies (Service Cloud Case ID: 02222733).
  • Fix for an issue where the admin user was not able to increase the conversational index memory in the ビジネスユーザー向け Automation Co-Pilot settings.
  • Fix for an issue where an error was displayed in the new process editor when users opened a process created in the previous editor that had parentheses and leading or trailing spaces in the Element ID field.
  • Fix for an issue where users were not able to see the form task after importing a process into private repository and running the process.
12 August 2025 Build 37468 (クラウド-Sandbox) includes the following:
  • Includes July 2025 package updates. See 2025 年 7 月
  • Introducing AI スキル page which displays AI スキル and AI スキル templates assigned to users. See スキル.
  • Amazon Q with Automation Co-Pilot feature is enhanced to allow users to upload multiple files at once to AI knowledge base for Automation Co-Pilot. See Automation Co-Pilot による会話型オートメーション.
  • Audit log feature is enhanced to allow users to search for audit logs for a maximum of 180 days. See 監査ログ.
  • Fix for an issue where users were not able to promote Bot from public repository by selecting the target URL and API key having angle brackets (< or >) (Service Cloud Case ID: 02221265, 02219560, 02221725, 02223059, 02223813).
  • Fix for an issue where the information on the User group tab on the Edit Process page in ビジネスユーザー向け Automation Co-Pilot kept refreshing when the Control Room language was set to a language other than English and deployment resource was not allocated (Service Cloud Case ID: 02222784).
  • Fix for an issue where automation failed when hidden variables were submitted via Automation Co-Pilot used as an embedded widget. (Service Cloud Case ID: 02222829).
  • Fix for an issue where users were not able to export Automation Co-Pilot tasks when the number of tasks was more (Service Cloud Case ID: 02223778).
  • Fix for an issue where automations failed to download Bot or dependencies when a child Bot using アクション in the 画像認識 パッケージ had scanned or manual dependency with its parent Bot (Service Cloud Case ID: 02220514, 02224111).
  • Fix for an issue where automations failed to download Bot or dependencies when using アクション in the レコーダー パッケージ (Service Cloud Case ID: 02184779).
  • Fix for an issue where users were not able to save changes after editing a schedule and no device pool was selected (Service Cloud Case ID: 02222783, 02224328, 02226718, 02227046).
  • Fix for an issue where automations failed when an アクション was disabled and included an empty or invalid condition (Service Cloud Case ID: 02221856).
  • Fix for an issue where automations continued to execute even after the scheduled Runtime time out value in certain scenarios (Service Cloud Case ID: 02219452).
  • Fix for an issue where users were not able to add or delete Run as users for roles (Service Cloud Case ID: 02224593, 02224668, 02225922, 02226081).
  • Fix for an issue where users were not able to import learning instances with validation feedback that included concurrent request and duplicate service fields (Service Cloud Case ID: 02213769).
  • Fix for an issue where a parent Bot failed to execute due to intermediate dependencies on itself (Service Cloud Case ID: 02215311, 02213762, 02220559, 02222147, 02224082, 02224963).
  • Fix for an issue where the bulk package update failed because actions used in a child Bot was not present in the previous version of the child Bot used in the parent Bot (Service Cloud Case ID: 02207757, 02225626, 02227363).
  • Fix for an issue where checking out a Bot failed when it contained large dependencies (Service Cloud Case ID: 02222733).
  • Fix for an issue where the admin user was not able to increase the conversational index memory in the ビジネスユーザー向け Automation Co-Pilot settings.
  • Fix for an issue where the mapped Number or Table element to a field of a form was not displayed after rendering the form in the process for the next tasks.
  • Fix for an issue where an error was displayed in the new process editor when users opened a process created in the previous editor that had parentheses and leading or trailing spaces in the Element ID field.
  • Fix for an issue where users were not able to see the form task after importing a process into private repository and running the process.
11 August 2025 Build 37468 (オンプレミス) includes the following:
  • Includes July 2025 package updates. See 2025 年 7 月
  • Support for custom certificate configuration during installation of OpenSearch (Linux installer). See OpenSearch の資格情報の追加.
  • Fix for an issue where users were not able to promote Bot from public repository by selecting the target URL and API key having angle brackets (< or >) (Service Cloud Case ID: 02221265, 02219560, 02221725, 02223059, 02223813).
  • Fix for an issue where the information on the User group tab on the Edit Process page in ビジネスユーザー向け Automation Co-Pilot kept refreshing when the Control Room language was set to a language other than English and deployment resource was not allocated (Service Cloud Case ID: 02222784).
  • Fix for an issue where automation failed when hidden variables were submitted via Automation Co-Pilot used as an embedded widget. (Service Cloud Case ID: 02222829).
  • Fix for an issue where users were not able to export Automation Co-Pilot tasks when the number of tasks was more (Service Cloud Case ID: 02223778).
  • Fix for an issue where automations failed to download Bot or dependencies when a child Bot using アクション in the 画像認識 パッケージ had scanned or manual dependency with its parent Bot (Service Cloud Case ID: 02220514, 02224111).
  • Fix for an issue where automations failed to download Bot or dependencies when using アクション in the レコーダー パッケージ (Service Cloud Case ID: 02184779).
  • Fix for an issue where users were not able to save changes after editing a schedule and no device pool was selected (Service Cloud Case ID: 02222783, 02224328, 02226718, 02227046).
  • Fix for an issue where automations failed when an アクション was disabled and included an empty or invalid condition (Service Cloud Case ID: 02221856).
  • Fix for an issue where automations failed unexpectedly when using レコーダー アクション (Service Cloud Case ID: 02221329, 02221869, 02221428, 02220604, 02223727, 02225650).
  • Fix for an issue where automations were not able to minimize the Bot running window and automations failed after updating to v.37 release (Service Cloud Case ID: 02220965, 02221833, 02221903, 02222203).
  • Fix for an issue where automations continued to execute even after the scheduled Runtime time out value in certain scenarios (Service Cloud Case ID: 02219452).
  • Fix for an issue where users were not able to add or delete Run as users for roles (Service Cloud Case ID: 02224593, 02224668, 02225922, 02226081).
  • Fix for an issue where users were not able to import learning instances with validation feedback that included concurrent request and duplicate service fields (Service Cloud Case ID: 02213769).
  • Fix for an issue where a parent Bot failed to execute due to intermediate dependencies on itself (Service Cloud Case ID: 02215311, 02213762, 02220559, 02222147, 02224082, 02224963).
  • Fix for an issue where the bulk package update failed because actions used in a child Bot was not present in the previous version of the child Bot used in the parent Bot (Service Cloud Case ID: 02207757, 02225626, 02227363).
  • Fix for an issue where checking out a Bot failed when it contained large dependencies (Service Cloud Case ID: 02222733).
  • Fix for an issue where the admin user was not able to increase the conversational index memory in the ビジネスユーザー向け Automation Co-Pilot settings.
  • Fix for an issue where the mapped Number or Table element to a field of a form was not displayed after rendering the form in the process for the next tasks.
  • Fix for an issue where an error was displayed in the new process editor when users opened a process created in the previous editor that had parentheses and leading or trailing spaces in the Element ID field.
  • Fix for an issue where users were not able to see the form task after importing a process into private repository and running the process.
18 July 2025 Build 37411 (クラウド-Sandbox) includes the following:
  • Fix for an issue where automations failed unexpectedly when using レコーダー アクション (Service Cloud Case ID: 02221329, 02221869, 02221428, 02220604, 02223727, 02225650).
  • Fix for an issue where automations were not able to minimize the Bot running window and automations failed after updating to v.37 release (Service Cloud Case ID: 02220965, 02221833, 02221903, 02222203).
16 July 2025 Build 37411 (クラウド) includes the following:
  • Fix for an issue where automations failed unexpectedly when using レコーダー アクション (Service Cloud Case ID: 02221329, 02221869, 02221428, 02220604, 02223727, 02225650).
  • Fix for an issue where automations were not able to minimize the Bot running window and automations failed after updating to v.37 release (Service Cloud Case ID: 02220965, 02221833, 02221903, 02222203).
11 July 2025 Build 37401 (クラウド) includes a fix for an issue where the mapped Number or Table element to a field of a form was not displayed after rendering the form in the process for the next tasks.
9 July 2025 クラウド release
6 July 2025 Build 37392 (クラウド-Sandbox) includes the following:
  • Introducing 次世代 Process Composer. See 次世代 Process Composer.
  • Support for Safari browser on macOS. See レコーダー パッケージ.
  • Fix for an issue where a field label was removed in Automation Co-Pilot when a user entered the field value or when the system automatically extracted the value (Service Cloud Case ID: 02213709).
  • Fix for an issue where any user with an Export or Import queues permissions and a queue participant or consumer was able to delete a queue (Service Cloud Case ID: 02213384).
  • Fix for an issue when you used the bulk update option for updating Excel の高度な操作 パッケージ to version 6.23.0, an extra character ($) was added to any variable that was used in the Convert Excel to PDF アクション (Service Cloud Case ID: 02212023).
  • Fix for an issue where users were not able to include credentials from the Control Room Credential Vault in their automations in certain scenarios (Service Cloud Case ID: 02210548).
  • Fix for an issue where data extraction from consignor form fields that did not have a defined header failed (Service Cloud Case ID: 02208490).
  • Fix for an issue where incorrect average time was displayed for automations that ran for more than 24 hours on the Longest running tab of the Top automations page (Service Cloud Case ID: 02206323).
2 July 2025 Build 37379 (オンプレミス) includes the following:
  • Introducing 次世代 Process Composer. See 次世代 Process Composer.
  • Support for Safari browser on macOS. See レコーダー パッケージ.
  • Fix for an issue where users were not able to use special characters such as pipe (|), colon (;), semicolon (;), and angle brackets (< >) in their passwords when setting up Service Credentials at the time of installing or updating their Control Room (Service Cloud Case ID: 02198414).
  • Fix for an issue where a field label was removed in Automation Co-Pilot when a user entered the field value or when the system automatically extracted the value (Service Cloud Case ID: 02213709).
  • Fix for an issue where any user with an Export or Import queues permissions and a queue participant or consumer was able to delete a queue (Service Cloud Case ID: 02213384).
  • Fix for an issue when you used the bulk update option for updating Excel の高度な操作 パッケージ to version 6.23.0, an extra character ($) was added to any variable that was used in the Convert Excel to PDF アクション (Service Cloud Case ID: 02212023).
  • Fix for an issue where users were not able to include credentials from the Control Room Credential Vault in their automations in certain scenarios (Service Cloud Case ID: 02210548).
  • Fix for an issue where data extraction from consignor form fields that did not have a defined header failed (Service Cloud Case ID: 02208490).
  • Fix for an issue where incorrect average time was displayed for automations that ran for more than 24 hours on the Longest running tab of the Top automations page (Service Cloud Case ID: 02206323).
  • Fix for an issue where automation failed when a child Bot with manual, scanned, or metadata dependencies was added as a dependent to a parent Bot (Service Cloud Case ID: 02213434, 02212482, 02213903, 02214567, 02220514, 02220569, 02220849, 02220829).
2025 年 6 月 18 日 オンプレミス release
2025 年 6 月 4 日 クラウド-Sandbox release
注: For documentation on previous builds of this release, see the PDFs available on this page: Automation 360 リリース ノート (ビルド バージョン) .

What's new and changed in each product

Navigate to the following pages for details on all the updates (what's new, changed, fixed, and limitations) in each product: