Flow failure may be bug?

[alee001]

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?

[Deenuji]

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]

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)

[Deenuji]

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]

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"

Sorry alee001 for hijacking.  hopefully this helps yours too 

[Deenuji]

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

[alee001]

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.

[ybicalways]

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]

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.

[Deenuji]

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]

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?

[alee001]

Why do I say that the problem of the PAD server may cause the error? Because today I found that some processes cannot be executed after multiple downloads, and the router needs to be restarted to return to normal (the network is normal).

[Deenuji]

Yeah, it's interesting problem to listen. If possible, can you raise this Microsoft where they can help to resolve this issue? Once you find the root cause don't forget to share with us 🙂

[alee001]

correct post:
The error is not [window cannot be found] but [button cannot be found].

[alee001]

The Internet is normal, suddenly the PAD is disconnected, and the process reports an error again [button not found]!😠

[alee001]

There is an updated version available this morning. Although the first execution flow is successful, but the second execution just now is the 16th loop error at the same position? !😥

[Deenuji]

Is that flow running in unattended mode or attended mode? If that working in unattended mode, just try to run multiple times in attended mode and see you can able to figure out the exact use for the above issue.

[alee001]

The process is to execute 20 independent VBA sequence files that have been opened (not opened by PAD). Every time after the button is repaired, an error will always be reported at the 16th loop at the same position the next day. (as pictured)

[alee001]

Forget about the previous process, I spent two hours re-establishing the process, and the result was the same error for no reason. This time (cannot find the button) I was stuck in the fourth loop. I am very disappointed that the bug has not been resolved.😖

[alee001]

I think it is likely to be a [Press button] bug. The following two captured the same VBA button, one is to click the button to automatically display the label description, and the other is to click the button quickly. Although the identification pattern is subject to the red line range, I suspect that [Press button] may have a deviation in the identification pattern, resulting in sometimes being unable to find the same button and reporting an error?