web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Flow failure may be bug?
Power Automate
Answered

Flow failure may be bug?

(0) ShareShare
ReportReport
Posted on by 422

The flow was normal until yesterday, but it suddenly reported an error this morning. I have tried to restart, but failed four times.

 

Why does a UI element [click the button in the window] get an error (the window cannot be found) every time it is executed to the 16th time (20 times in total) in the loop?

 

Finally, it is normal to delete it and re-establish it. This incident has happened for the second time this month, is there a bug?

  • CU16071609-1 Profile Picture
    6,255 Moderator on at

    Hi @alee001, Could you please share some screenshot and exact issue details? You're getting window cannot be found or click failed(failed to get windows)?

  • ybicalways Profile Picture
    13 on at

    I am having the same issue with my 20 daily automations.

     

    Correlation Id: 15277509-b8d4-4d93-a02f-d9aae99a08ae

    Exception of type 'Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Exceptions.WindowNotFoundException' was thrown.: Microsoft.PowerPlatform.PowerAutomate.Desktop.Actions.SDK.ActionException: Window wasn't found ---> Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Exceptions.WindowNotFoundException: Exception of type 'Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Exceptions.WindowNotFoundException' was thrown.
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Window.WindowsActions.FindWindowByRetractionMode(String windowSelector, String childWindowSelector, IntPtr handle, String windowTitle, String windowClass, UIWindowRetractionModeEnum uiWindowRetractionMode, Int32 automationImpl)
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Window.WindowsActions.ResizeWindow(String windowSelector, String childWindowSelector, IntPtr handle, String windowTitle, String windowClass, Int32 newWindowWidth, Int32 newWindowHeight, Int32 uiWindowRetractionMode, Int32 automationImpl)
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Proxy.LocalAutomationRuntime.ResizeWindow(UIRuntimeElement window, IntPtr handle, String windowTitle, String windowClass, Int32 windowWidth, Int32 windowHeight, FindWindowBy windowMode)
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Proxy.UIAutomationRuntimeRouter.Invoke(MethodInfo targetMethod, Object[] args)
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Reflection.DispatchProxyGenerator.Invoke(Object[] args)
    --- End of remote exception stack trace ---
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.Proxy.RemoteAutomationRuntimeProxy.Invoke(MethodInfo targetMethod, Object[] args)
    --- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Reflection.DispatchProxyGenerator.Invoke(Object[] args)
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Actions.ResizeWindowBase.<Execute>b__29_1(IAutomationRuntime r, UIRuntimeElement e)
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Common.UIAutomationActionBase.PerformLocalAutomation(Action`2 action, UIControl control, Boolean logAction)
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Actions.ResizeWindowBase.Execute(ActionContext context)
    --- End of inner exception stack trace ---
    at Microsoft.Flow.RPA.Desktop.Modules.UIAutomation.Actions.ResizeWindowBase.Execute(ActionContext context)
    at Microsoft.Flow.RPA.Desktop.Robin.Engine.Execution.ActionRunner.Run(IActionStatement statement, Dictionary`2 inputArguments, Dictionary`2 outputArguments)

  • CU16071609-1 Profile Picture
    6,255 Moderator on at

    Thank you for your details. Is that your 20 daily automations using same windows app? If you know exactly where you get this error in PAD flow some screenshot or code would be helpful

  • ybicalways Profile Picture
    13 on at

    I have separate automations running with different Excel files (instances).  Every time we are running, we get this error - "(the window cannot be found)"

     

    The window is in reference to what is open in the desktop automation.  I have those Excel files getting moved around and resized.

    I am using "Find window mode: "By title and/or class"

     

    ybicalways_0-1689692820326.png

     

    Sorry alee001 for hijacking.  hopefully this helps yours too 

  • CU16071609-1 Profile Picture
    6,255 Moderator on at

    Based on the information provided, I understand that occasionally, the Excel window is not found during your PAD flow execution. Due to the limited knowledge of your flow, I recommend incorporating a "wait for window" action to verify whether Excel has opened before proceeding with the "resize window" action, as shown below. This will help ensure a smoother execution of the automation process

     

    Deenuji_0-1689694042414.png

     

  • alee001 Profile Picture
    422 on at

    The error message has been eliminated, and the button [Captial 2] in the figure below is a new UI element capture.


    Last week was also another button error that had to be recaptured.

    螢幕擷取畫面 2023-07-18 233415 拷貝.jpg

  • ybicalways Profile Picture
    13 on at

    I believe you are correct in the delay.  The main issue is I have been running these automations successfully for a year.  Something has changed in the programming of "Desktop Automate" or "Excel"  to cause this delay.  The files themselves open like normal.  But those instances do not populate to "Desktop Automate" in a timely fashion.

     

    I think this is DEV issue.  I hope it gets figured out soon as this will cost me hours a week just keeping up with errors.

  • alee001 Profile Picture
    422 on at

    The button reporting the error is the button inside the VBA userform.

     

    The strange thing is that if you don't re-capture the button with UI elements, sometimes it will return to normal when it is turned on the next day.

  • CU16071609-1 Profile Picture
    6,255 Moderator on at

    I would suggest that, while recapturing the elements, duplicate your desktop flow and re-capture the failed elements in new flow then once its working fine then compare same element with all attributes with old desktop flow element attributes so that we will understand what is exactly changed during the recapture process. 

  • alee001 Profile Picture
    422 on at

    I have a backup (copy) process. I have compared the same location and element content and found that it is exactly the same. I wonder if the problem with the PAD server caused the error?

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.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 259 Super User 2026 Season 2

#2
11manish Profile Picture

11manish 227 Super User 2026 Season 2

#3
Valantis Profile Picture

Valantis 134 Super User 2026 Season 2

Last 30 days Overall leaderboard