Review what's new and changed and the fixes and limitations in Automation Co-Pilot for the v.40 release.

What's new

AI Agent discovery and deployment in Automation Co-Pilot
Automation Co-Pilot now supports unified search and deployment for both Processes and AI Agents within the Assistant conversational tab.
  • AI Agents published to the Public repository are now processed with the same summary generation and metadata extraction logic used for processes.
  • Relevant descriptions and dependency information are generated and stored in VSS for improved indexing and search ability.
  • Assistant search results are now filtered to surface only Processes and AI Agents, excluding other automation types (such as API Tasks and Bot Tasks) to maintain relevance and usability.

This enhancement delivers a consistent discovery and launch experience, enabling business users to interact with AI Agents in the same streamlined manner as Processes.

Goal-based agents in Automation Co-Pilot
Real-time in-progress indicators for dynamic form API Tasks

Real-time in-progress indicators are now added for API Tasks triggered by dynamic form rules. Users can now see visual feedback (For example, spinners, busy states) on buttons and form fields when background API Tasks are executing, including cascading updates across multiple elements. The affected fields are temporarily disabled during processing and automatically re-enabled upon completion. This enhancement improves transparency, reduces accidental interruptions, and ensures more predictable form interactions during asynchronous operations.

Test Process (API Task in process)

Service Cloud Case ID: 02304723
Styles tab for advanced form customization

We’ve introduced a new Styles tab in the Form Composer, enabling developers to directly customize form appearance using CSS. This enhancement provides greater control over layout and styling, allowing you to meet advanced branding and UI requirements beyond standard visual editing capabilities.

Add custom style to a process automation

What's changed

Multiple task assignment in Co-Pilot Web

Team managers and administrators can now assign or reassign multiple tasks at a time directly from the Tasks page in Co-Pilot Web. This enhancement streamlines task distribution during peak processing periods, reducing manual overhead and operational bottlenecks. Delivered in response to customer feedback, the feature is expected to significantly improve workload management efficiency and reduce labor waste associated with manual task reassignment.

Assign multiple tasks
File sync status visibility and error insights for Amazon Q indexing

You can now view the Amazon Q sync status of each file directly within the AI Knowledge file table. A new Sync status column displays whether a file is Synced, Not synced, or Failed, enabling users to quickly verify indexing status and identify files that require attention. This enhancement improves operational transparency for Amazon Q indexing and allows knowledge managers to quickly detect incomplete or failed ingestions, troubleshoot issues, and maintain reliable search results within the knowledge base.

Manage AI knowledge base for Automation Co-Pilot
Improved date clarity and cross-interface consistency in [co-pilot] Embedded/Assistant

Standardized date display across [co-pilot] Embedded and Assistant to use the named month shorthand format, aligning with [co-pilot] Web. Dates on Activity history, Assigned and Requested tasks pages now appear as MMM DD YYYY (For example, Mar 8 2026), replacing the ambiguous numeric MM/DD/YYYY format.

Fixes

Fixed an issue where you perform the following steps:
  1. Create a form with a Checkbox group element and set default values.
  2. Create a Task Bot with list and dictionary output variables.
  3. Create a process, add the Task Bot and an Approval task, and assign the created form.
  4. Map the list and dictionary variables to the checkbox group in the approval task.
  5. Save and run the process.

The Checkbox group elements in the approval task now correctly retain the dynamically mapped values after task submission, rather than reverting to the form’s defaults.
Users will now continue to see the appropriate inline notification pill button after refreshing the page, regardless of whether the automation includes input variables.

Previously, the inline notification pill button in the Conversational interface was replaced with a static Automation launched successfully message after a page refresh.
File uploads for Learning Instance processes submitted directly in Automation Co-Pilot chat work as expected, and users no longer see an error message after submission.

Previously, users encountered an error message after submitting a Learning Instance (Document Automation) process with file inputs directly from Automation Co-Pilot chat.
Forms now open in a dedicated right-hand pane, ensuring the entire form is immediately visible and eliminating the need for additional scrolling.

Previously, users opening a form task notification in Automation Co-Pilot would initially see only a partial form, requiring manual scrolling to view the full content.
Sending additional prompts is now temporarily disabled while the assistant is responding, ensuring that all submitted messages are properly captured and displayed.

Previously, some chat messages were not displayed if users submitted multiple prompts in quick succession before receiving a response in Automation Co-Pilot Assistant.
Forms now render consistently with other execution entry points (Automation Co-Pilot and Automations tab), providing a polished and space-optimized user experience.

Previously, in the Conversational Assistant where forms with fewer elements rendered within a fixed half-height container in the right pane, leaving the lower section blank and positioning the Submit button midway on the screen.

Hidden tasks can now be opened from task page and re-hidden without generating Invalid Task Id error.
Pagination is now displayed correctly on the Recycle Bin page, allowing users to navigate through recycled requests as expected.

Previously, pagination controls were not visible on the Recycle Bin page after deleting a large number of requests.
File upload using File type input variables now works correctly in Automation Co-Pilot.

Previously, file upload using File type input variables was not working correctly with public process in Automation Co-Pilot.
Hidden elements are no longer rendered inside forms displayed in the right pane of the chat assistant.

Previously, forms containing elements marked as hidden were incorrectly rendered as visible in the chat assistant right pane during automation execution.
Tables are now displayed with improved alignment and structural consistency in the chat interface.

Previously, certain tables retrieved through Conversational Assistant (RAG responses) were not rendered correctly in the chat interface.
File uploads for learning instance processes submitted directly in Automation Co-Pilot chat work as expected, and users no longer see an error message after submission.

Previously, users encountered an error message after submitting a learning Instance (Document Automation) process with file inputs directly from Automation Co-Pilot chat.
The Forms rules engine has been corrected to ensure validation rules are consistently re-evaluated when field values are modified programmatically.

Previously, the IsEmpty validation rule was not triggered when a TextBox field was programmatically reset to its default (empty) value through a rule action (For example, using button click).
The approval task rendering and completed step display have now been updated to ensure that checkbox values mapped from list variables are correctly preserved and displayed.

Previously, only selected value is getting displayed on approval task.
Fixed an issue where Dropdown Multi-Select elements failed to retain dynamically mapped values in Approval tasks. When you created a form with default values (for example, a, b, c), overrode them in a Form task (for example, p, q, r), and mapped those values to an Approval task, the Approval task did not preserve the selected value at runtime.

With this fix, the Approval task now correctly retains and displays the dynamically mapped Dropdown Multi-Select selections after the Form task is submitted.
Fixed an issue where RadioButtonGroup elements did not display dynamically mapped values at runtime.

Previously, when you created a form with a RadioButtonGroup containing default values and used that form in a Bot task or Approval task, mapping list and string output variables (from a Task Bot or process inputs) to the Available and Picked option fields did not work as expected. After running the process, the RadioButtonGroup continued to show only its default values and ignored the mapped inputs.

With this fix, the RadioButtonGroup now correctly displays the mapped list and string values during process execution.
Fixed an issue where importing a process with a Filter task caused the Value to filter field to incorrectly remap to the Any type when originally mapped to a Dictionary or Record variable. The Process editor now preserves the correct variable mapping during import and no longer displays an error.
Fixed an issue where Dropdown elements did not display dynamically mapped values at runtime.

Previously, when you created a form with a Dropdown containing default values and used that form in a Bot task or Approval task, mapping list and string output variables (from a Task Bot or process inputs) to the Available and Picked option fields did not work as expected. After running the process, the Dropdown continued to show only its default values and ignored the mapped inputs.

With this fix, the Dropdown now correctly displays the mapped list and string values during process execution.
Fixed an issue where a Dropdown element did not retain dynamically mapped values when passed from an Approval task to a subsequent Form task using the Any:asAny expression. Previously, the Form task reverted to the Dropdown’s default configuration at runtime, causing mapped values to be lost. The Dropdown now correctly displays the dynamic values.
Automations with an initial step containing forms now run as expected when triggered from chat.

Previously, users encountered failures when starting such automations, or requests were created without loading the required initial form.
Scrollbar now appears correctly for long (more than 388 characters) comments. Also, text is properly contained and displayed within the comments field.

Previously, users were unable to view long comments properly in the approval task.
Users can now directly open links within Microsoft Teams Co-Pilot without switching to a browser. It improves usability of forms containing embedded HTML links. With this fix, users can now open hyperlinks from Rich Text Editor (RTE) elements in the following scenarios:
  • When the form is in read-only mode.
  • After the form step is completed.
  • When the RTE element is non-editable, even if the form is in a pending state.

Previously, hyperlinks rendered within RTE elements were not actionable in the Microsoft Teams Co-Pilot environment.

Note:
  • Right-click actions (For example, open in new tab/window) remain unsupported in Microsoft Teams.
  • Hyperlinks are not clickable when the form is in a pending state and the RTE field is editable.
The input area is now fully isolated per conversation thread. Any unsent attachments are cleared when switching threads or starting a new conversation, preventing cross-thread carryover.

Previously, unsent file attachments in the input area persisted when users switched to another conversation thread or created a new one.
The system now correctly handles pre-update orchestration job records after update, ensuring scheduled background jobs continue to run and workflow executions are reconciled and cleaned up successfully.

Previously, Orchestrator quartz background jobs could fail continuously after updating due to NULL values in the invocation_source_id field for pre-existing orchestration records, causing workflow reconciliation, expiry checks, and deployment status checks to stop processing.
Users can now successfully submit the initial step in Automation Co-Pilot workflows even when processes contain input Record variables with Window and Credential sub-types.

Previously, users encountered submission errors while running public processes in V1 and V2 when Record variables with Window or Credential sub-types were rendered in the initial step form. In some scenarios, failures occurred only when the variables were selected.
The inline notifications are now consistently shown when form tasks are assigned, including when they occur after a validator step.

Previously, users did not receive assignment notifications in chat under this scenario, although notifications worked correctly in other cases.
Chat responses now display only user-friendly automation names and relevant execution details. Internal Bot IDs are no longer exposed during conversational automation interactions.

Previously, Bot IDs were displayed in chat during multi-turn automation execution flows when users attempted to run recommended automations.
The assignedTo{id} meta variable now correctly returns and displays the associated user ID in form tasks.

Previously, the meta.assignedTo.id variable returned an empty value when mapped to form task inputs, preventing assigned user details from being displayed in processes.
The deletion behavior now correctly removes associated connectors, ensuring the workflow reflects the intended state.

Previously, in the Process editor where the Remove items action from the toolbar did not fully update the workflow layout. When deleting a Form task, connector lines were incorrectly retained due to automatic edge re-connection during layout rendering.

Limitations

When a Radio Button input from an Approval task is mapped to a Form task's Radio Button variable, the default options such as ( a, b, c) are not rendered in the Form step at runtime. The issue occurs specifically when string variables are used as the picked option in the Approval task.
The If Else block incorrectly triggers the Else branch when a DateTime conditional uses the "Equal to" operator with a specific date, time, and timezone (example, 03/11/2026, 01:30 AM, IST UTC+5:30). Even when the user submits a matching date in the Form task, the process routes the request to the Failed End node instead of the Completed End node.

Workaround: Set the target time in the IF block to 12:00 AM to avoid encountering this issue.
If you are on using Automation 360 v.28 or earlier version and encounter duplicate Submit buttons in form step, you need to remove these duplicate buttons manually.

Service Cloud Case ID: 02211874
When a File element is added inside a Dynamic Area element and rendered through an interactive form, file upload functionality might fail.
When using the Number elements (without selecting Allow Negative Value) in combination with a Formula element, invalid character entry might not trigger immediate validation and can affect formula results.
When a process uses a start‑step form with a Time element, IF condition that compare this Time value to a static DateTime value using Equal To do not evaluate as true. Even if the user enters a Time that matches the time portion of the static DateTime, the condition still fails.
When a Multiselect drop-down field from an Approval task is referenced in a subsequent Form task, the selected and available options might not render correctly.

Workaround: To fix this issue, use the original variable mapped in the Approval step such as$list_string_avail$), instead of referencing the Approval input as

amp;Approval{input}{MultiSelectDropdown0}$.

This workaround avoids the V1 list-to-string conversion issue while preserving correct values.
Links embedded within the Rich Text Editor (RTE) element might not function as expected in Microsoft Teams if the HTML anchor tag does not include the target="_blank" attribute.

Workaround: Explicitly include target="_blank" in all the anchor tags within the HTML content.
Users might observe validation errors displayed within the process editor for some variable conversions after checking in processes to the Public repository.
Note: There is no functional impact with this limitation.
When a role was removed from a process, users associated with that role could still see the process in their list for several hours. Attempting to launch the process during this period might result in an unauthorized access error.
In some cases, the Conversational Assistant might not render clickable hyperlinks from content ingested via AI Knowledge (For example, PDFs). When prompted for links (such as, Give me the algorithm guides link), the assistant might return a summarized reference instead of the actual hyperlink.

In the Co-Pilot Admin interface, users might be unable to create a new tag if it is a sub-string of an existing tag. For example, if a tag such as document-automation already exists, attempts to add tags like document, automation, or auto will fail.
Administrators can disable the LLM Responses in Co-Pilot settings from Control Room administration settings; however, end users still see and can use the File upload capability in the Co-Pilot interface.
Dynamic form element values might not be retained when a Form task is cancelled, which can result in inconsistent or missing variable mappings in subsequent Form tasks and read-only views.

In Conversational Automation, users might still be able to interact with recommended automation pill buttons and access archived chat threads after license consumption limits have been exceeded. This can allow limited interaction with automation listings and conversation history even when the license is over consumed.

In Conversational Assistant, the file-count attachment icon displayed on sent messages might disappear after switching to another conversation thread and returning to the original conversation. As a result, users might temporarily lose visibility into the list and count of files previously attached to that message.