Power Automate for desktop - Build 2608

This article describes the new features, improvements and fixes to existing functionality that are included in this build.

Installer version 2.71.112.26212 - Microsoft Store version 11.2608.112.0 updates

New features

• User mapping credentials are now available to be created in the portal of Power Automate and are supported in the 'Get credential' action, allowing a desktop flow to automatically use the application credential mapped to the user account that the flow runs under. Such credentials can be selected during authoring and are resolved to the matching credential values at runtime, for both attended and unattended runs.

  This feature will gradually roll out during August.

  Dataverse solution version 1.10.12.0 or later is required. To confirm the latest version used, go to the Power Automate portal, then select the Solutions page, go to the History tab, and search for the key term ‘MicrosoftFlowExtensionsCore’. Check the Version column to verify the most recent version update.

• New AI Builder actions have now been introduced in the respective module, allowing desktop flows to natively analyze text sentiment, detect the language, and translate text.

Enhancements & Improvements

• Several enhancements have taken place for the AI-assisted UI automation repair experience, including:

  • a new context option 'Run from here with AI-assisted UI Automation Repair (Preview)' in the flow designer, allowing users to start a debugging session from the selected action with the AI-assisted UI automation repair experience being active,
  • the UI element picker window now being displayed during recapture so that the capture can be reviewed or cancelled,
  • repaired selectors being named 'AI-generated selector' in the UI elements repository to be easily distinguished,
  • and a note in the run summary clarifying that suggested repairs are kept in the flow's unsaved version until the flow is saved.

• Self-healing is now also supported for window manipulation actions in UI automation.

• The self-healing summary reported for each flow run in the portal now also includes the total number of self-healing attempts that were made, along with the number of successful repairs that were applied.

• Several enhancements have taken place for the version comparison experience, including filtering the compared items by change type, adding or removing the versions under comparison, minimizing the comparison window independently of the flow designer, refreshed icons, spacing, and tab behavior, and full support for the light, dark, and high contrast appearances.

• An option to show more details by displaying all available information for a UI element has now been added to the UI element picker, listing every property exposed by the element and allowing it to be copied, which makes it easier to troubleshoot UI automation issues.

• The Region actions have now been updated to offer custom color swatches.

• A search box is now available in the text editors of Power Automate for desktop, opened with CTRL+F, offering match case, whole word, and regular expression options, a match counter, and navigation between matches, in the light, dark, and high contrast appearances.

• A sign-in latency diagnostic has now been added to the Power Automate troubleshooter, reporting how long Windows user profiles take to load on the machine, so that slow sign-ins affecting unattended runs can be identified.

• The performance of packaging and loading desktop flows has now been improved, resulting in faster flow opening and saving.

• The performance of UI automation using the UIA3 accessibility framework has now been improved, resulting in faster detection of UI elements.

• Downloads of the .NET runtime during installation are now retried automatically, reducing installation failures caused by transient network conditions.

Repaired functionality

The following list details issues in Power Automate for desktop that are now resolved:

• An issue where viewing the value of an input or output variable that had a default value, before running the flow, resulted in an error, along with an issue where cancelling the value visualizer could still persist the discarded value, have now been resolved.

• An issue where editing a flow variable stored an unintended default value for numeric and Boolean variables, along with an issue where default values were not retained when saving a flow through 'Save as', have now been resolved.

• Users can now set a custom value for input and output variables during debugging, directly from the value visualizer.

• An issue where a web element captured during AI-assisted UI automation repair was not highlighted and validated correctly has now been resolved.

• An issue where the console and the flow designer could crash unexpectedly while navigating with the keyboard, most commonly in the flows list, has now been resolved.

• An issue where child flow runs were attributed to the wrong parent run in the Power Automate portal, when a parent flow started multiple child flows at the same time, has now been resolved.

• An issue where flows using UI element event triggers could fail unexpectedly when the target element was no longer available has now been resolved.

• An issue where the installation of Power Automate for desktop failed on certain Windows 10 machines has now been resolved.

• An issue where loading or selecting an environment occasionally failed with an unexpected error has now been resolved.

• An issue where the actions generated by Copilot were not displayed in the Copilot pane, showing an error message instead, has now been resolved.

• An issue where flows generated by Copilot were not corrected automatically, when a generated action contained an invalid input, has now been resolved.

• An issue where removing a tag that can't be deleted left the flow properties panel unresponsive, requiring the console to be closed from Task Manager, has now been resolved. A message now indicates which tags can't be removed.

• An issue where the keyboard focus was trapped in the read-only preview fields of several action editors, such as 'Filter data table', 'Join data tables', 'Filter list', and 'Run .NET script', has now been resolved.

• An issue where runtime DLP validation was being applied to example flows, which aren't associated with a Power Platform environment, has now been resolved.

• A more appropriate error message is now displayed when an input argument of the 'Run desktop flow' action can't be evaluated, indicating which input caused the failure.

• An issue where concurrent flow runs on the same machine could fail with a script not found error has now been resolved.

• An issue where desktop flows with canvas app and environment variable dependencies failed to be imported as part of a solution has now been resolved.

• An issue where a UI element referencing a global variable failed to be resolved inside a local subflow, both at runtime and as a validation error in the flow designer, has now been resolved, via a local to global variable scope fallback.

Other announcements

• The 'Run Power App' action is now generally available in all cloud environments, including sovereign clouds.

Return to the all version availability page.