'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Power Automate Desktop Cannot Find SAP UI Elements
Question details
The user encounters an ElementNotFoundException in Power Automate Desktop when attempting to interact with SAP UI elements during an automation flow.
- Product
- Power Automate Desktop
- Device & OS
- not provided
- Scenario
- Running a recorded desktop automation where window titles, indexes, or application sessions have changed since the initial recording.
- Observed behavior
- The automation fails because the recorded selectors no longer match the current state of the SAP application, triggering an element-not-found error.
Ensure that your SAP application is fully loaded and logged in before executing the automation flow. Verify that no unexpected pop-ups or system messages are blocking the target UI elements.
Recapture SAP UI Elements Using Stable Selectors
Replace dynamic or changing UI attributes with stable selectors so Power Automate Desktop can consistently identify the target elements.
When an application's state changes between sessions, relying on dynamic attributes like session IDs, changing window titles, or coordinates often leads to an ElementNotFoundException. Adjusting the selector to use static, unique identifiers will make your automation significantly more robust.
Launch your SAP application manually and navigate to the exact screen and state where the automation process fails.
Open Power Automate Desktop, navigate to the UI elements pane on the right sidebar, right-click the failing element, and select 'Recapture'.
Click on the recaptured element to open the selector builder. Uncheck any dynamic attributes (such as specific window titles that change, indexes, or session-specific IDs) and keep only stable attributes like Name, Class, or ID.
In your flow designer, drag and drop a 'Wait for window' or 'Wait for UI element' action immediately before the interaction step to ensure the SAP interface is fully active.
Resolve Profile and Correlation ID Errors
If your UI automation failure is accompanied by a lost cloud profile or correlation ID error, you must recover your account state via the official community.
Boost Your Productivity with WPS Office
If you are troubleshooting Microsoft ecosystem tools and working heavily with data exports, consider switching to WPS Office. It is a highly compatible, lightweight, and completely free alternative to Microsoft Office that perfectly handles all your Word, Excel, and PowerPoint needs.
- 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the software: Run the downloaded executable file and follow the on-screen prompts to complete the installation in minutes.
- 3. Open your existing documents: Launch WPS Office and directly open your existing Word, Excel, or PowerPoint files without losing any formatting.
Frequently Asked Questions
Why does Power Automate Desktop throw an ElementNotFoundException in SAP?
This exception occurs because the recorded UI element's attributes (like a dynamic window title, index, or session ID) change when the SAP application is restarted, causing Power Automate to lose track of the original element.
How can I make my SAP UI selectors more reliable in Power Automate?
You can improve reliability by editing your selectors in the UI elements pane to use static attributes. Avoid using dynamic text, relative coordinates, or session-specific IDs. Instead, rely on unique control IDs, classes, or fixed names.
Will adding delays fix UI automation errors?
Yes, adding 'Wait for UI element' or explicit delays before an interaction ensures that the application has fully rendered the element before Power Automate attempts to click or extract data from it.
What should I do if my Power Automate profile loses access or generates a correlation ID error?
If you encounter correlation ID or invalid cloud type errors after signing in, you will need to contact the Microsoft Power Automate Community. Their specialists can assist with account profile recovery and routing password resets to the correct email address.
