Announcements
Running bots in unattended mode can sometimes be tricky, especially when dealing with UI elements and OCR-based actions. Here are some steps and best practices to help resolve these issues:
Service Mode Installation: Ensure that the bot is installed in service mode. This is crucial for unattended automation as it allows the bot to run with the same rights as the user under which it is registered.
Screen Resolution and Visibility: Unattended bots often fail to interact with UI elements if the screen resolution changes or if the screen is not visible. Make sure the screen resolution is set correctly and that the bot has access to the session.
UI Element Identification: For the 'Click UI element in window' action, try using more robust selectors. Ensure that the selectors are dynamic and can adapt to changes in the UI.
OCR Actions: OCR-based actions require the screen to be visible to capture the text. Since OCR might not work well in unattended mode, consider using alternative methods like selectors or data scraping techniques.
Move Mouse to Image: This action can be unreliable in unattended mode due to changes in screen resolution or visibility. Ensure that the images used are clear and distinct. Adding waits or delays before this action can sometimes help.
Error Handling and Logging: Implement detailed error handling and logging to capture the exact issues. This can help in diagnosing why certain actions fail and provide insights for troubleshooting.
Testing and Debugging: Run the bot in attended mode to identify any issues and then switch to unattended mode. Compare the behavior and make necessary adjustments
I understand how challenging it can be when Power Automate Desktop doesn't recognize a specific UI element. Here are some suggestions that might help:
Use the Recording Feature: Power Automate Desktop's recording feature can be very useful for interacting with UI elements. You can record the actions you want to automate, and the recorder will track mouse and keyboard activity in relation to UI elements. Here's how you can do it:
Verify UI Element Selectors: Ensure that the selectors for the UI elements are accurate and haven't changed. You can use the UI element picker to capture and validate the selectors.
Recapture the UI Element: Sometimes, recapturing the UI element can resolve recognition issues. Try capturing the element again and replacing it in the action .
Edit Selectors Manually: If the selectors are dynamic, you might need to edit them manually to make them more robust.
Check Element Availability: Ensure that the UI element is available on the screen during the execution of the flow.
Use UI Elements Pane: Manage and organize your UI elements through the UI elements pane in the flow designer. This can help you keep track of all the elements used in your flow .
I hope these suggestions help! If you need further assistance or have any other questions, feel free to ask
If the response is helpful to you, a like or mark as the correct solution. thank you so much!
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Haque 569
Valantis 484
Vish WR 460
