Unanswered

Unattended flow wont logout when error occurs

(1) Share

Report

Posted on by Wereley9

Hello,

I'm having a problem when using Power Automate Desktop unattended flows. I have a flow that runs every 30 minutes and sometimes an error occurs. The problem is that when an error occurs Power Automate wont logout of the machine. When that happens, every flow that comes after get a timeout error (I have a 15 minutes timeout).

Why is this happening? Power Automate shouldnt logout even when it gets an error?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (6)

Answers (0)

Sort by

eetuRobo 4,579 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Are you sure its logged in after the first fail? What is the error message you get when you think its still logged in?
If Power Automate is logged in to the machine I think the other desktop flows should stay in queue until it has logged out of the previous session.

Was this reply helpful? Yes No
Wereley9 14 on at

Like
a
(1)

Report
Copy link

Link copied!

The image above shows the desktop flow execution. For some reason, the desktop flow executed for almost 3 days, even when the cloud flow failed. I don't know why this happened.

Every desktop flow that came after stayed in the queue, failing after 15 minutes because of the timeout. I just cant understand why it executed for 3 days, even with a timeout.

I will monitor the executions throughout the week.

Was this reply helpful? Yes No
eetuRobo 4,579 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

That is weird.
When you say you have set Timeout you mean in the "Run a flow built with Power Automate for desktop" -cloud actions settings? And have you checked that its syntax is correct? I think for 15 minutes its like so: PT15M

Was this reply helpful? Yes No
Wereley9 14 on at

Like
a
(1)

Report
Copy link

Link copied!

Yes, it's exactly like that:

Was this reply helpful? Yes No
Wereley9 14 on at

Like
a
(1)

Report
Copy link

Link copied!

And now I got an error in the desktop flow execution and the following executions are stuck in "queued":

I don't have any other flows running at the moment and no user is using the machine. When looking at the cloud flow execution, I have this "invalid parameters", but I think it's a bug:

Was this reply helpful? Yes No
David-BCG on at

Like
a
(1)

Report
Copy link

Link copied!

I have been running into this exact issue for the last couple of weeks. After the flow runs, the user will not be signed off from the target server by PAD (this seems to happen at random regardless of whether the flow is successful or not). This results in the next run failing since the user is already logged in. This is a new issue that has not presented itself for the last year while this flow has been running successfully. For now I am just restarting the server daily whenever this issue starts back up. Upon restarting the server, the issue seems to go away for a few hours, but not more than 24 hours before coming back. Seeking a more permanent solution.

Was this reply helpful? Yes No