Unattended run not finishing, not reporting errors

(0) Share

Report

Posted on by powerautomator3

I have a desktop flow that runs succesfully in a VM in about 15 minutes. We made a cloud flow that triggers it, and runs in unattended mode in the same VM.

Now when it gets started, something weird happens and the run can take hours but reports no progress or errors.

Attended run works fine from cloud flow, but in production we need unattended.

How can I debug what is happening? maybe some action is getting stuck for some reason?

In the PA site there's also some problem where I think you should be able too see the actions as they progress, but I see nothing (screenshot taken after 30mins of run)

Categories:

Using flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

eetuRobo 4,501 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

You cant see the actions progress in real time in Power Automate Run status. The action log will only get uploaded after the Power Automate Desktop run has finished.

I recommend adding some "Take screenshot" -actions that you save to oneDrive folder. That way you can check those while the flow runs. Also you might want to add some logging with PAD writing to text file on OneDrive folder after certain steps so you can see on what action the flow can do and where it stops.

Also add some error handling and if you have error handling make sure it doesn't go in to infinite loop with the error handling. Also add timeouts on those actions that have it available like "Wait for window content"

You might want to check Anders Jensens video about best practices. That video Simple logging (20:36) and Advanced logging (58:32) section in it: https://www.youtube.com/watch?v=QjrxLPg_TdI&ab_channel=AndersJensen

Was this reply helpful? Yes No
powerautomator3 56 on at

Like (1)

Report
Copy link

Link copied!

Thanks Eetu, some good tips there! I found out that after you cancel the run, you can see the actions list and that was useful for debugging. In my case I made the unattended screen resolution larger and changed all web element clicks to 'non-physical', that seems to help if the elements are out of view

Was this reply helpful? Yes No