Power Platform Community Forum Thread Details

I have been having issues with the "Wait for Window" Action within PAD Flows recently and its starting to drive me crazy. I am using this action when downloading a file from a website and waiting for the "Save As" window to appear. When running an automation attended it does not seem to have an issue and the UI element can be found, but when run unattended this step fails almost every time. I have played around with the screen selector, but this becomes difficult to test when the action works perfectly attended, but not unattended. If anyone has a workaround or any specific pointers that would be great.

Categories:

Power Automate Desktop

Hello,

Have you checked the screenshot that PAD takes when the flow fails (make.powerautomate.com portal look at the failed desktop flow run logs and the last action that has status error)? Is the window visible in the error screenshot or is there something different than when you run it in attended?

In your title you talked the problem being in different VM's. Are you using same VM when you have tested in both attended and unattended? Are you doing the attended tests in VM1 and then trying to do the unattended run in VM2 that fails? If so I would try attended run also in VM2 to see if there is some machine specific issue and not run mode issue. And also what if you try to recapture the selector in that VM2 then does it give different looking selector?

Can you show screenshots of your flow where the error happens and screenshot of the screen selector?This way we might be able to point out some possible issues with it.