UI Flows Unattended - Gateway Timeout

(0) Share

Report

Posted on by erea

Hello All,

I am having an issue running UI Flows in unattended mode.

I created a web UI flow and in attended mode it works flawlessly. If i am logged into the server i can see UI Flows open chrome and perform all the coded actions.

The issue is when im not logged into the server - the UI flow never runs or completes. The flow fails with the below error after 2 minutes.

{

"error": {

"code": "GatewayTimeout",

"message": "The gateway did not receive a response within the specified time period."

}

What is preventing the UI flow from logging in or creating the user session?

The On-Premises gateway works fine, however it is running under the default NT Service account. Does that need some kind of special access?

Categories:

Power Automate Desktop

All responses (22)

Answers (1)

Sort by

v-litu-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @erea,

Could you please show me your Flow configuration?

You could have a try to change the service account for the on-premises data gateway to check whether it could work:

https://docs.microsoft.com/en-us/data-integration/gateway/service-gateway-service-account

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
erea 39 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

I tried changing the gateway account to the account i remote in as to view "attended" jobs and it still does not work.
Same result, attended works fine but unattended does not run at all.

My configuration is below but please let me know if you need more.
Thank you for the assistance
erea 39 on at

Like
a
(1)

Report
Copy link

Link copied!

Just trying to keep this alive as i cannot the figure the issue out still.
This is a huge issue with Power Automate right now.
erea 39 on at

Like
a
(0)

Report
Copy link

Link copied!

so, weve identified the general cause of the problem. It looks like there is some kind of server security policy causing an issue.

Everything looks fine when we investigate and cannot determine what is blocking Power Automate from creating the user session in unattended mode.

If anyone has any ideas, please let me know.
Geralt Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @erea
thank you for your time reporting this problem.
Currently we considered it as a bug.
I'll keep on monitoring the bug and keep you posted.
mg2019 15 on at

Like
a
(0)

Report
Copy link

Link copied!

Did you get this resolve? I am having the same issue with a new UI flow.

Thanks.
erea 39 on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you, and please let me know if there is anything that can be done in the meantime.

As i mentioned, this is a security policy issue and going through each 1 by 1 is proving to be a huge time sink.
mg2019 15 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for your reply. Honestly, I was having high hope that the UI flow will automate a manual process that causes some bottleneck.

I have tried to run the UI flow in unattended and attended mode with no success. The only way to run it is in attended mode with the windows screen unlock, since if it is locked throws an error. But there is GPO that locks the screen when it is idle.

Thanks.
Geralt Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @mg2019

Thank you for your response.
Please walk through this document to have a better understanding about those modes: https://docs.microsoft.com/en-us/power-automate/ui-flows/run-ui-flow#run-ui-flows-unattended-or-attended.

In case you are having a problem running UI flow and have never got succeeded please re-install the newest UI flow and try again.

After that if you are still facing the error, i would suggest you to open a ticket with Microsoft Support maybe i can take a look and help you.

Regarding the issue while running in Unattended mode. Currently, we are able to reproduce the issue and we are actively working on the investigation i'll keep you posted.

thank you.
mg2019 15 on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @Geralt

Thanks for your reply. I followed that link but with no success. I created a ticket at Microsoft and a support guy called me
to check the issue and he could not resolve it.

This is the Service Request #: 120062924000075

Thanks