Automation Workspace v.41 release - Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.41 release.

Review what's new and changed, and the fixes and limitations in Automation Workspace for the v.41 release.

What's new


Control Room, devices, and Bot Agent
Unused property cleanup with Secure recording (Service Cloud Case ID: 02296764) Authorized users can now configure UI element actions to automatically remove unused properties, including binary large objects (BLOBs), from new and older automations. This enhancement helps reduce unnecessary data retention, including data that might contain sensitive information. Secure recording mode
Create custom dashboards permission A new Create custom dashboards permission is available in role management, under the Observability section. This permission controls which roles can create and manage custom dashboards with detailed operational metrics. By default, it is not granted to new roles and is enabled for the AAE_Admin role. The Observability section groups all observability-related permissions, including View operations data and its sub-permissions. Admins can grant or revoke the Create custom dashboards permission for any role to control access to dashboard creation. Feature permissions for a role
Custom time range filter for ACC dashboards You can now filter dashboard metrics by a custom date range on the ACC home page. In addition to the preset time filters, a Custom option is available on the following dashboard tabs: Processes, API Tasks, Devices, Licenses, and AI Governance. When you select Custom, specify a start date, start time, end date, and end time. The dashboard refreshes automatically to display metrics for the selected range. Filter dashboard metrics by custom date range
Public API for package usage insights Automation 360 now provides a public API to retrieve package usage information, enabling administrators and developers to identify automations that use a specific package or package version. The API supports filtering, pagination, and export-friendly responses, making it easier to track package dependencies, improve governance, and automate package management workflows through CI/CD pipelines. This enhancement also aligns with existing user permissions and provides detailed usage visibility similar to the Package visibility page in Control Room. Package usage through APIs
Operations center and custom dashboard Automation 360 administrators and process owners can now use the operations center to monitor and manage their entire Agentic Process Automation environment from a single location. The operations center primarily includes the following three dashboards: Monitor - View real-time activity across your Agentic Process Automations. Activity - Track in-progress and historical execution details. Insights - Access key metrics for your agents, processes, and automations. Use these dashboards together to optimize processes, improve operational efficiency, and quickly address failed or blocked automations. ACC home page for administrators Note: Operations center is not available out of the box and must be enabled separately. Contact your Automation Anywhere Customer Support for assistance on enabling this feature.
Option to add an annotation in editors Annotations can now be added directly in the Process, Bot, and API editors, improving documentation, readability, and maintainability by allowing developers and process owners to comment on specific elements of a process flow or automation logic. About annotations
Enhanced Quick add in the Bot and API editors The Quick add feature in the Bot and API editors now supports faster action insertion with improved search guidance and keyboard navigation. Contextual help text: The search box displays the placeholder text. Type an action or package name to find it to guide your search. Keyboard navigation: After typing in the search box, press the Up or Down arrow keys to move through results, then press Enter to add the selected action to the canvas. Using Bot editor
Multiple external key vault integrations Automation 360 now supports configuration and management of multiple external key vaults within a single Control Room for Enterprise license customers. Authorized users can create, view, update, and delete multiple vault connections (including multiple instances of the same vendor, such as AWS Secrets Manager, Azure Key Vault, or BeyondTrust Password Safe), and use any active vault for supported use cases such as Auto-Login and system-level credentials. In addition, an authorized user can assign specific external key vault connections to individual lockers. This lets different lockers retrieve credentials from different vaults based on organizational, environmental, or security requirements. When existing Automation 360 deployments are updated to this release or a later version, Automation 360 automatically retains their current external vault configuration. This ensures backward compatibility while providing greater flexibility and control over credential management across the enterprise. Integrating with multiple external key vaults
On-Premises Windows Installer supports Delinea Secret Server integration Automation 360 On-Premises Windows Installer now supports Delinea (Thycotic) Secret Server as an external key vault option, enabling you to securely retrieve database and service account credentials directly during the installation process. On-Premises initial installation using Delinea Secret Server
On-Premises Windows Installer supports BeyondTrust Password Safe integration Automation 360 On-Premises Windows Installer now supports BeyondTrust Password Safe as an external key vault option. This enhancement allows you to securely access and retrieve database and service account credentials directly during the installation process. On-Premises initial installation using BeyondTrust Password Safe
OAuth authorization support for Azure Key Vault via API Gateway Automation 360 Cloud now supports OAuth-based authentication for connecting to Azure Key Vault through a customer-managed API Gateway. You can configure an API Gateway endpoint as the vault base URL and enable OAuth authorization using the client credentials grant type. The system automatically acquires an access token and injects it into outgoing requests. This is an optional configuration, while the existing direct Azure Key Vault integrations in the Cloud deployment continue to work without any changes. Cloud integration using Azure Key Vault
Enterprise license support for multi-vault in Automation 360 Control Room Automation 360 now supports an enterprise license capability called Multi Vault Support for external key vault integrations. When this enterprise feature is enabled, a single Control Room can be configured to use multiple external key vault connections at the same time. This allows organizations to bring credentials managed for different teams, systems, or use cases to Cloud automation. Enterprise Platform
Introduced a new feature license pack called Automation Platform Core This release introduced a new feature license pack called Automation Platform Core, alongside the existing Enterprise Platform offering. Automation Platform Core delivers enhanced enterprise-grade platform capabilities to manage uber-scale automation, performance, and users for enterprise customers and automation partners. Automation Platform Core
Volume license usage tracking for offline licenses The Control Room now supports volume license usage tracking for offline licenses. Volume licenses such as document automation pages, documents will now be counted and enforced in an offline license setup. Note that AI credits and document automation credits are not currently supported with offline licenses.
License drill-down in offline mode The License page for offline Control Rooms now supports drill-down for all license types. Administrators can click into any license item to view detailed usage, with a simplified layout showing Purchased, Used in this CR, and Balance columns. The drill-down displays only the This Control Room tab, as cross–Control Room views do not apply in offline environments.
Offline license group management Offline license groups on the Group Distribution page are now clearly identified in the table with the label Offline group. Unlike Cloud license group, which authorized users can create, edit, or delete with an active Enterprise Platform license, offline license groups are always view-only regardless of the license status. They cannot be created, edited, or deleted from the Control Room. For Cloud license group, if the Enterprise Platform license expires, authorized users can view and delete existing groups, but cannot create new groups or edit existing ones until the Enterprise Platform license is renewed. Besides, the Group Distribution and Account Utilization tabs are now displayed regardless of whether the Enterprise Platform license is purchased, providing visibility into license data across all license types. License group management \| Create a license group
Submit API Tasks to the Agentic App Store (formerly Bot Store) You can now submit API Tasks directly to the Agentic App Store (formerly Bot Store), making them available for discovery and reuse alongside other automation assets. This enhancement streamlines the publishing experience by providing a consistent submission workflow across automation types. By enabling API Tasks to be shared through the Agentic App Store (formerly Bot Store), organizations can more easily promote reuse, accelerate automation development, and improve access to commonly used integrations and services. Submit bots or packages to Agentic App Store (formerly Bot Store)
Nested API Tasks You can now create nested API Tasks using the new API Task package. The Run action in the package enables you to invoke a child API Task from within a parent API Task. The parent API Task can pass input values to the child API Task, and save the response data to variables. This package allows you to break down complex workflows into maintainable units by creating modular and reusable API Tasks. API Task package
Pause and resume event triggers You can now pause and resume event triggers that contain one or more web triggers. This capability enables you to pause event triggers temporarily during maintenance, outages, or unexpected failures in the connected SaaS application. When paused, the event trigger retains its configuration but does not process any incoming events. When you resume a paused event trigger, the event trigger starts processing events normally.
Challenge-based validation for Incoming webhook trigger The Incoming webhook trigger now supports challenge-based validation to verify the ownership of listener URLs. Use the Verify listener ownership option to enable this validation. When enabled, the external application sends a challenge code to the listener URL and delivers the event data only when the listener URL acknowledges and sends back the challenge code. This validation is available only for Monday and Slack. Challenge-based webhook validation
Parse and extract specific key-value pairs from incoming trigger data The web triggers now parse and extract one or more key-value pairs from the incoming trigger data. Use the variable mapping option in the Multiple variables tab to extract values from specific keys and use them in downstream actions. This option improves trigger performance, eliminates unnecessary data in the payload, and can reduce the associated costs.
Support for additional content types in Incoming webhook trigger The Incoming webhook trigger now supports event data in more content types, such as plain text, XML, multipart form data, and form-urlencoded data. This capability enables the Incoming webhook trigger to process event data from external applications that deliver it in these formats. In the case of multipart form data containing files, it processes only the metadata of the files. Similar to JSON-based event data, Audit log records the event data as Bot run by trigger event type in key-value pair format.

What's changed


Control Room, devices, and Bot Agent
Tenant-specific support for identical custom packagesMulti-tenant package management now supports custom packages and connectors with identical names and versions across different tenants within the same deployment. Package validation is enforced at the tenant level, preventing conflicting uploads within the same tenant while allowing independent package management across tenants. This enhancement improves package isolation, governance, and flexibility for enterprise multi-tenant environments. Custom package upload validation
Package selection support for Agentic App Store (formerly Bot Store) submissions When submitting automation assets to the Agentic App Store (formerly Bot Store), you can now review and select the packages to include as part of the submission process. The submission experience also provides clearer visibility into the packages included with an asset, helping ensure that all required dependencies are accurately identified before publishing. This enhancement improves the publishing workflow and provides greater control over the assets and dependencies shared through the Agentic App Store (formerly Bot Store). Submit bots or packages to Agentic App Store (formerly Bot Store)
Rehydrating a Control Room high-availability (HA) cluster (Service Cloud Case ID - 02299292) Starting from this release, rehydrating a Control Room high-availability cluster — primary and disaster recovery nodes — to new servers is certified. This includes prerequisite backups, Elasticsearch state cleanup, Ignite cluster table reset, and post-migration validation steps. Administrators can move Control Room to new hardware (OS update, hardware refresh, datacenter migration, hypervisor/cloud change, and so on) without losing cluster state. Automations, users, roles, and historical audit logs are preserved, and end users see no disruption beyond the planned maintenance window since they land back on the same Control Room they left with the change being the new infrastructure. Rehydration of Control Room cluster to new servers - Windows
Existing permissions updated to view and manage holiday calendars (Service Cloud Case ID: 02332221) Starting from this release, the following Activity permissions are updated to include the ability to view the holiday calendars: View my scheduled bots and holiday calendars View ALL scheduled activity from my Folders and holiday calendars View ALL scheduled activity and holiday calendars Additionally, a new permission called Manage holiday calendars can be added by the Control Room administrators to enable the users to create, view, edit and delete holiday calendars. Activity
Enhanced WLM work item aggregation WLM dashboards now support hourly aggregated work item reporting for analytics. Queue-level completed and failed work item statistics are consolidated into dedicated reporting tables, ensuring dashboard data remains available even after work item purging. Aggregation runs automatically at regular intervals with optimized batch processing for improved scalability and reporting performance.
Progress of a process execution in the General tab Starting from this release, the General tab now displays runtime and deployment details for the process, including a live progress bar that updates as the process runs. For processes and AI Agents, the progress bar reflects 50% until execution is complete.
Poller in Universal web trigger package is now generally available Poller in the Universal web trigger is now generally available. Configure a Poller to poll a URL at specific time intervals for events in any SaaS application and start an automation when any event occurs in those applications.
Enhanced filtering and customization in Historical and In Progress page The Historical and In progress page now includes additional filters and customization capabilities to provide greater flexibility in monitoring automation execution, including completed Process requests and AI Agent executions. Users can now filter results by Automation type, Activity type, and Team/Role, alongside other customizable view options. Historical activity \| Monitor and manage automation activities in Automation 360
Automation Credit drill down page UI updates The Automation Credit drill down page in Control Room is now updated. Service Credits Used is now renamed to Service Units Used, Automation Credits Used is now renamed to Document Automation Credits Used / AI Credits Used, a new column for Document Automation Credits Used / AI Credits Used has been added, and all the consuming services are now listed in the usage details, including those with zero consumption. This provides complete transparency with consumption data.
Enhanced AI credit consumption tracking We have now refined how AI credits are consumed for Automation Anywhere-provided model interactions and AI Agent executions. AI credit calculation now incorporates token-level metering, counting both input and output tokens for each execution. One Automation Anywhere-provided model interaction includes up to 2,000 tokens, and one AI Agent execution includes up to 50,000 tokens. Exceeding these ceilings charges additional credits per block. Token-based ceilings for AI Agent executions apply only when the AI Agent is built using an Automation Anywhere-provided model. Automation Anywhere provided models in AI Agent Studio \| Licensing model for AI Agents
Support for Master Key rotation in Credential vault Key management operations for AWS key management system and Google Cloud Platform now include annual enabling of Master Key rotation and Data Key re-encryption in the Control Room, thereby enhancing compliance and security. Master Key rotation
Process editor: Auto-mapping of conditional paths to Branch Exit in Split and Merge branches When you add or modify If/Else/Else-If nodes inside a Split and Merge branch, the Process editor now automatically connects each conditional path to the Branch exit. With this enhancement: Each conditional path (If, Else, Else-If) is automatically connected to the Branch exit when the node is created or modified inside a branch. If you add steps to a conditional path, the auto-mapping updates so that the last node in the path connects to the Branch exit. If you delete the last node in a conditional path, the connection is re-established from the new last node. This change reduces the effort of manually connecting every conditional path end to the Branch exit, minimizes modeling errors, and ensures predictable merge behavior across all conditional path configurations.
Default primary button in Form tasks When you create a process using Form task, the Form task requires at least one primary button for the process to be saved. Now when you add a new Form task to a process, the editor automatically enables a default primary button labeled Submit. This prevents save-blocking validation errors and allows you to continue building the process without interrupting your workflow to configure button settings.
Change in API Task execution measurement The Automation Anywhere Cloud Service license now measures the API Task executions in 20-second increments instead of 60-second increments. An API Task that runs for 20 seconds or less counts as one execution. Each additional 20-second increment counts as an additional execution. Consumption model
Enhanced display of advanced search results and errors across editors The Assistant panel in the editors now shows results from Issue browser, Advanced search, and Search and replace in a consistent, unified format. Each result row displays the node type (Trigger, Element or Action number) and the number of matches, making it easier to review search results, understand errors and warnings, and navigate to affected lines. Assistant in Process editor
Change in handling of Bot Agent Bulk Registration token The Bot Agent Bulk Registration token is now associated with the system and not linked to any user within the Control Room. As the system autogenerates this token, the token remains unaffected when the user who originally generated it is deleted. In the case of multi-tenant deployments, the system autogenerates this token for each child tenant. On-demand API Tasks use this system-generated token during runtime. Starting from this version, the existing tokens are automatically associated with the system.

Feature deprecation


Deprecation of support for keys in Hot key trigger for macOS The Hot key trigger does not support the following keys in macOS: Fn-Delete Clear Numpad Enter

Fixes


After updating to this release, Activities > In Progress tab no longer displays invalid entries. Service Cloud Case ID: 02332931, 02333024, 02332964, 02333000, 02333034, 02332715, 02332960
Fixed an issue where reloading the Form field in a Form task cleared the variable mapping configured under the Available options field for dynamic form elements, such as radio buttons and check boxes.
Fixed the issue in SAP BAPI Run custom workflow advanced action when the Import table type is selected. The parameter values entered in the table are not retained after clicking Apply. This action causes incomplete processing due to mismatched parameters. Service Cloud Case ID: 02315507
Fixed an issue where packages with the Preview image option displayed an error icon and a blank preview when you edited a bot with Secure Recording enabled. Service Cloud Case ID: 02332307
Folder names and permission check boxes are now aligned correctly when creating or editing a custom role on the Roles > Bots screen. Previously, the folder name and check box spacing were misaligned, making folder permission selection unclear. Service Cloud Case ID: 02296927
Code Analysis policy assignments now remain intact when users delete folders from their private workspace. Previously, deleting a matching private workspace folder could remove the policy assignment from the public workspace folder. The policy was not deleted, but it had to be manually reassigned. Service Cloud Case ID: 02297392
External links in Automation 360 now include the `rel="noopener"` attribute where applicable. Previously, some external links could open without the noopener attribute, which is recommended for links that open in a new tab or window to help prevent reverse tab-nabbing. This update adds the attribute as a security-hardening measure and does not change the link navigation behavior. Service Cloud Case ID: 02293393
You can now export all roles from the Control Room even when system-created roles are disabled in the database. Previously, clicking the Download button to export all roles failed with an unexpected error, and the exported file in the Historical tab displayed a failed status. This occurred when disabled system roles were encountered, although exporting only custom roles worked as expected. Service Cloud Case ID: 02282962
After updating to this release, you can switch the default device directly from the Devices menu when the Bot Agent service on the current device is stopped. Service Cloud Case ID: 02285785
The Audit log now displays the specific error message correctly that reflects the cause of the scheduled automation deployment failure, making it easier to troubleshoot. Service Cloud Case ID: 02285731
Logs generated using the Log to Server command in Cloud deployments are now retained as expected and remain visible in Activity > Historical > Historical activity > Logs page. Previously, logs were automatically deleted after 48 hours, causing them to disappear from the Logs page. Service Cloud Case ID: 02320957
HTTP TRACE and TRACK methods are now disabled on port 4576 in On-Premises Control Room deployments, resolving security scan findings related to Cross-Site Tracing (XST) vulnerabilities. Service Cloud Case ID: 02272831, 02279651, 02280244, 02300544, 02301132, 02301940
You can now allocate Bot Creator licenses successfully in Cloud Control Room when licenses are available. Previously, some Cloud Control Rooms showed the error, even when the License page showed available licenses. Service Cloud Case ID: 02292938, 02293185, 02293188, 02292879, 02293338, 02293545, 02293342, 02292435, 02293195, 02293584, 02293399, 02294052, 02295187, 02295261, 02296418, 02297507
When an automation execution completes, the status of the corresponding request no longer displays as In Progress and the request status now updates correctly to reflect the completion of the associated automation task. Service Cloud Case ID: 02312174, 02315381, 02314243
The Document Automation license settings and features now appear correctly in the Cloud Control Room for POC tenants. Previously, it was not showing up in their Cloud Control Room, causing the feature to appear greyed out on the License page, and inaccessible despite being purchased. Service Cloud Case ID: 02306334
License groups can now be edited successfully when assigning or removing runtime licenses. Previously, editing license groups could fail with the message `Cloud License Server is currently unavailable. Please try after some time`. This prevented users from assigning or revoking licenses for tenants. Service Cloud Case ID: 02311954
User details on the License details page now display correctly in all the supported languages. Previously, user details did not appear when the Control Room UI language was set to a language other than English. Service Cloud Case ID: 02286409
Repository check-in processing has been improved to correctly synchronize bot content, version metadata, and checkout status. Successful check-ins now properly release the checkout lock, increment the bot version, maintain accurate version comparison history, and ensure repository state remains consistent across Public and Private workspaces. Previously, in certain scenarios, bot check-in operations did not complete correctly. Users could experience bots remaining in a checked-out state, version numbers not incrementing after check-in, inconsistencies in version comparison results, and updates appearing in the Public workspace without the repository metadata being properly synchronized. Service Cloud Case ID: 02292749, 02296718, 02315179, 2315290, 02312910, 02304428, 02319870, 02325615
Form dependencies are automatically updated during check-in. When Image or Logo elements are removed, their associated image dependencies are correctly cleared, ensuring that only active assets are retained and exported with the form. Previously, when an Image or Logo element was removed from a form and the form was checked in, the associated image dependency was not removed. Service Cloud Case ID: 02275586, 02308080
Export activities are now consistently displayed in Historical activity page for authorized users regardless of whether users have the View activity from user's folder permission, provided they have the required access and activity permissions. Previously, users with the View activity from user's folder permission could not see export activities in Historical activity page, while users without this permission could see them. Service Cloud Case ID: 02287326, 02293874
The queue schedules now retain the configured times across Daylight Saving Time (DST) transitions. Previously, when DST ended, the start and end times configured for WLM queue processing schedules shifted back by one hour. Service Cloud Case ID: 02282801, 02281639
Workload Management now correctly processes CSV-based work item uploads, even when queue scheduling jobs encounter timing inconsistencies. Previously, in certain situations, uploading work items through a CSV file using the user interface or API could appear to complete successfully but the work items were not added to the target queue. Service Cloud Case ID: 02301266
Workload Management now validates current device pool membership before assigning work items. Devices that have been removed from a device pool are no longer eligible to receive or process work items, ensuring that automations run only on active devices configured for the associated queue and deployment. Previously, in certain WLM deployments configured to run on a device pool, work items could continue to be assigned to and processed by devices that had already been removed from the associated device pool. Service Cloud Case ID: 02307570
Workload Management now automatically resumes processing of work items as soon as their configured hold duration expires. Previously, work items placed in an On hold state did not always resume processing immediately after the configured hold duration expired. Service Cloud Case ID: 02307157
Workload Management (WLM) now refreshes run-as user assignment information correctly when automation configurations are updated. Previously, in user-based WLM deployments, work items could experience unexpected delays before being assigned, even when the associated run-as user and device were available. Service Cloud Case ID: 02301624
Selected columns are now displayed consistently across Public and Private Workspace views. The Folder column is shown only when Search within subfolders is enabled, providing relevant folder path information only when applicable and improving the overall search experience. Previously, in workspace search results, selected columns were not consistently displayed due to column configuration synchronization issues. Additionally, the Folder column appeared even when folder path information was not relevant to the search. Service Cloud Case ID: 02301285, 02302038
Form rule processing is now improved to correctly handle interdependent controls, ensuring visibility and state changes are applied as expected when users interact with Button elements. Previously, in some forms, rules that controlled the visibility or state of Button elements did not execute correctly when multiple controls referenced each other, resulting in unexpected behavior. Service Cloud Case ID: 02303118
The Process Composer Create a Request action now supports Boolean input variables, allowing processes to receive the intended Boolean values from the automation. Previously, when creating process requests from automations, boolean input values were not always passed correctly, which could result in processes using unintended default values. Service Cloud Case ID: 02298093
Access controls are now properly enforced, preventing users without the required licenses or permissions from accessing private workspace files through the repository API. Previously, users whose Developer or Creator licenses had been revoked could still access files in their private workspace through the repository API.
All the Git-related audit event types are now displayed consistently with the correct capitalization as Git across audit logs. Previously, audit event types in Control Room repository displayed inconsistent naming for Git-related events, with some entries appearing as git instead of Git.
Execution mode and Queue timeout settings are now preserved after process edits, ensuring process configurations remain intact. Previously, these settings were not retained after editing and saving processes in the legacy process editor, causing errors when reopening the process.
Interrupted bulk bot updates now correctly reflect their final status after recovery, preventing stale In Progress entries and allowing users to continue bot updates and check-ins. Previously, if a bulk bot update was interrupted, it could remain incorrectly marked as In Progress on the Bot update page after recovery completed. Service Cloud Case ID: 02307899, 02332201
The Automation status widget on the Control Room home page now accurately reflects the status of automation executions. Completed automations no longer remain incorrectly displayed as Running, and the running automation count aligns with the active executions shown on the In progress activity page. Previously, The Automation status widget could incorrectly display completed automation executions as Running. Service Cloud Case ID: 02297081, 02308279, 02292811, 02308279
WLM deployment now handles the required configuration correctly, allowing automations to deploy successfully and work items to be picked up and processed as expected after an update. Previously, after updating to Automation 360 v40, WLM automations might fail to deploy and work items could remain in the Ready to run state without being picked up for processing. Service Cloud Case ID: 02329059, 02333386, 02329363
When you permanently delete a request from the Requests page, any associated tasks with the request are also removed to maintain consistency across the Control Room. Previously, deleting a request did not delete its associated tasks creating inconsistency across the Control Room. Service Cloud Case ID: 02300482
Fixed the issue in the Automation Command Center (ACC) dashboard where the Automation Status on the Overview tab of the Automation 360 Homepage incorrectly displayed zero values despite active or failed bot activity. Service Cloud Case ID: 02312193, 02326843
Processes that use Split/Merge with a Go To action can now compile and run successfully when the Go To action jumps to a node after the Merge action. Previously, such processes could fail to compile with a `FAILED_PRECONDITION` error, preventing the process from running. Service Cloud Case ID: 02329736
The folder path now correctly displays Agentic App Store when saving an AI Skill as a template or creating an AI Skill from a template. Previously, in such case, the folder path incorrectly displayed Bot Store.
The Password field now accepts more than 75 characters, enabling authentication with Bitbucket API tokens. Previously, the Password field for an external Bitbucket integration accepted a maximum of 75 characters, preventing you from using longer API tokens.
The APIs now enforce the required validations to prevent updating manual dependencies or editing bots in a Public workspace, promoting bots from a Private workspace, and exporting bots from a Private workspace. Previously, APIs incorrectly allowed restricted operations on bots in Private and Public workspaces.

Limitations


On the process designer canvas, icons for element titles such as Task, Conditional, and Event do not display. Only the element names are visible.
In the process map section of the Activity details panel, some properties are missing for processes in the In progress and Historical activity views.
When you move a trigger node to a different swimlane of the root node and add a new trigger node while the moved trigger node is selected, the new trigger node is not added to the same swimlane as the moved trigger node. Overlapping nodes are not resolved automatically.
In Process editor, the annotation icon and badge do not display correctly on process nodes. The annotation icon does not stay inline with the count. Other icons do not wrap to the next line as expected. In some cases, icons are pushed out of the node or hidden within it.
When you use Quick add to insert an If-Else element inside a Split and Merge, the If-Else element is not positioned correctly on the canvas.
When you click the documentation icon from the tooltip or the right panel for a task, the documentation link opens in a new browser tab instead of the Resource center (in-product help widget).
In Process editor when you detach an edge from a node handle and attempt to connect it to another handle on the same node, the edge does not attach even if the target handle is valid. Moving either node does not reset the handle.
In the Advanced search and Search and replace panels, search results display the label Action with a line number and match count instead of the correct Element or Trigger label.
When creating a process with Form, Approval, or Document Validation tasks and defining process-level or task-level business attributes containing underscores (_), an issue occurs after saving and refreshing the page. The business attribute key displays an error, and underscores are replaced with spaces in the editor. This issue is observed only after a page refresh.
When submitting a bot or template to the Agentic App Store (formerly Bot Store), the Submit button might remain disabled even when all required information has been provided and no mandatory actions are pending. Workaround: To fix this issue, navigate to the Packages tab and then return to the submission workflow. The Submit button is refreshed and available when all submission requirements are satisfied.
When you open the Lockers tab from the External Vault and edit any locker, the Credentials tab displays the list of credentials allocated to the locker. However, you cannot add or remove credentials. Workaround: Navigate to Credentials under Manage on the left menu, go to the Locker tab, select the locker listed under External Vault, and select the credential you want to remove.
When you navigate to the Credentials page under External Vault tab, the option to edit an existing external credential vault connection is not available, even if you have the required role permissions. Workaround: Navigate to Credentials under Manage on the left menu and edit an existing external credential vault connection.
When customizing search result columns in Automation Workspace, the position of the Folder column might not be preserved if the column layout is modified while Search within subfolders is disabled and later re-enabled. As a result, the Folder column might appear at the end of the table instead of its previously configured position.
An expired queued automation execution might continue to appear in the Queued state on the Activity > In progress tab for up to 6 hours before it moves to the Activity > Historical tab.
When checking in a bot with nested dependencies in a private workspace, dependencies of a cloned child bot might not appear in the Available dependencies or Selected dependencies lists. For example, consider the dependency chain Task1 → Task2 (cloned) → Task3. When you check in Task1, Task3 does not appear in either the Available dependencies or Selected dependencies list, even though it is a dependency of the cloned Task2.
After restoring an AI Agent from an external Git repository, the View references and dependencies tab might not display the AI Agent's associated tool dependencies, even though the restore operation completes successfully. Note: This limitation affects dependency visibility only.
When restoring API Tasks from an external Git repository, the original MIME types associated with API Tasks are not preserved. As a result, restored API Tasks will be shown as Task Bots in the Control Room.
When you view older versions of a checked-in API Task that has an AI Skill as a dependency, the AI Skill appears in the API Task editor page but does not appear on the Dependencies tab. This behavior occurs when you remove the AI Skill from the API Task in the second version and then add the AI Skill as a dependency in a subsequent version.
The Override request attributes (optional) section is displayed for a Merge node. However, when users add business attributes using this option, the configured values do not override the existing request-level business attribute values.


Limitations from previous releases
In Connector Builder, when you import JSON while defining the request or response payload, a UI rendering issue prevents the Map Attribute values from appearing automatically. The Connector Builder displays the attributes only in edit mode. Workaround:Connector Builder Not Displaying Map Attribute Details in View Mode.

Updates to the interface


Automation Workspace
The Automation Credit drill-down page in Control Room has been updated with the following improvements: Service credits used column is now renamed to Service units used for clarity, and a new column for Document Automation Credits Used / AI Credits Used is now added to the Consuming Services table in the Usage details page. Automation Credits Used column under This Control Room tab is now renamed to Document Automation Credits Used / AI Credits Used.