Unable to run flows in unattended mode

(0) Share

Report

Posted on by MOHX_05

Hi Community,

Has anyone had issues with running flows in unattended mode recently?

I have some flows that were previously running in attended and unattended mode without issues, but after the last PAD update, I've been having difficulties running flows in unattended mode.

Runtime machine shows that machine is connected both on the local machine and on power automate portal but when I try to create a connection using the server credentials, it returns internal server error and issue has been persistent for almost a week now.

I have disconnected and reconnected runtime server machine, but this didn't fix the issue, I also tried to initiate a new connection, but issue still persists.

Although, flows are running fine in attended mode. Please I need urgent assistance with this issue.

Any help or suggestions is welcomed.

Here's the error

"Test connection failed. Details: Connection failed: [Machine e949bc8c-98db-45fa-8133-39d124c63fee] Connection failed: Encountered internal server error.. Correlation id: d22e5e83-c236-441a-8164-accea253f322"

Categories:

Power Automate Desktop

I have the same question (0)

All responses (10)

Answers (0)

Sort by

JK-30071416-0 on at

Like
a
(0)

Report
Copy link

Link copied!

OK...I was starting to go crazy thinking I was the only person having this problem. I'm seeing the exact same error and have found no resolution.

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Have you tried reporting this to MS support?

Was this reply helpful? Yes No
MOHX_05 18 on at

Like
a
(0)

Report
Copy link

Link copied!

@Agnius Yes, I have raised issue with MS support and there's been no adequate feedback for about 2 weeks now. This is now starting to create doubts in my client mind

Was this reply helpful? Yes No
MOHX_05 18 on at

Like
a
(0)

Report
Copy link

Link copied!

@jjknudsen have you found any workaround for this issue?

Was this reply helpful? Yes No
JK-30071416-0 on at

Like
a
(0)

Report
Copy link

Link copied!

I have not found a workaround and also have a case opened. I shared my screen with them yesterday and they tried all the usual stuff and said they needed to escalate internally.

Was this reply helpful? Yes No
JoaquinHome 8 on at

Like
a
(0)

Report
Copy link

Link copied!

any updates on this issue? i am having the same problem ever since their last update. please help.

Was this reply helpful? Yes No
MOHX_05 18 on at

Like
a
(0)

Report
Copy link

Link copied!

@JoaquinHome there's been no so far, they've shared quite some numbers of workaround but none has worked so far

Was this reply helpful? Yes No
MOHX_05 18 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @jjknudsen @JoaquinHome I just found a resolution to the issue. Reverting back to V2.37 fixed the issue. I would recommend you downgrade to v2.37

Let me know if you need the link to download it, I can share the one I got from Microsoft.

Was this reply helpful? Yes No
JK-30071416-0 on at

Like
a
(0)

Report
Copy link

Link copied!

I just received the download this morning and am rolling back as we speak. Thanks for the offer!

Was this reply helpful? Yes No
MOHX_05 18 on at

Like
a
(0)

Report
Copy link

Link copied!

however, there are some constraint with downgrading to the older version such as not being able to edit or run some flows that were created using the newer version. Although the MS SE suggested opting in for a custom v2.39 version which is still in testing phase.

Was this reply helpful? Yes No