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 / PAD unattended flow wa...
Power Automate
Suggested Answer

PAD unattended flow wait for window content

(0) ShareShare
ReportReport
Posted on by 20

i have a PAD flow that automates an action in a Window application, I then have a wait for window content action. 

 

When running in attended execution the wait action works, however when in the unattended mode the action times out. 

 

The length of time it should need to wait for is around 5-10 mins. 

 

Any ideas on this behaviour?

 

thanks

John

I have the same question (0)
  • Sanju1307 Profile Picture
    4 on at
    I know its been like 4+ years since you posted this question but looks like Microsoft came up with a different problem this time.
    in my case, same action but "Fail with timeout error" field doesn't have any effect at all, the robot waits indefinitely no matter what value I set in the Fail with timeout error field.
    This happens in attended mode for me.. I havent checked unattended mode as it doesnt make any sense to me.
  • Suggested answer
    eetuRobo Profile Picture
    4,579 Super User 2026 Season 1 on at
    Check the logs of the failed unattended flow run. It should save screenshot. Is the window content visible in the screen when the flow has faile on the "Wait for window content" -action?
    Like so:

     
     
    It could be that the window content is not visible in the screen because the screen resolution is much smaller than in the attended run. Or there is some other reason why the flow is having trouble in unattended run.

    https://learn.microsoft.com/en-us/power-automate/desktop-flows/how-to/set-screen-resolution-unattended-mode


    Is the machine that unattended run is being executed same as when you have executed the run successfully on attended mode? If not then maybe some element is different on the unattended machine(different version of windows or the application that is being automated).


    Is the exactly the same application when running in attended and unattended? Maybe the attended run is using the applications dev/test environment and unattended is using production environment.  Then the problem could be that the UI elements are little different on the dev environment that you captured them from for the "Wait for window content" -action vs in the production environment.

    ps. I know this is an old post but since it poped up on the first page I thought might as well answer. Hopefully you figured it out already.

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 June Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 262 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 167

#3
Haque Profile Picture

Haque 154

Last 30 days Overall leaderboard