Answered

Sharepoint connection when running Power Automate unattended

(0) Share

Report

Posted on by SHLJV

Hello everyone,

I am trying to run my process in unattended mode. But whenever I try to run a flow which needs to connect to Sharepoint I receive the following error:

Access to some desktop flow connectors wasn't validated. Verify the following connections: XXXXXXX_shared_sharepointonline_XXXXXXXX and try again.

When opening the flow in PAD the activities related to Sharepoint are all validated and working. When running the process attended it is working fine. When running the proces from PAD directy it is working fine. However whenever I try to run unnattended I get this error.
The account has acces to the right pages in sharepoint, the license is connected to the flow, the machine is connected..

Is there anyone who has a a solution for this?

thank you in advance!

Categories:

Power Automate Desktop

I have the same question (0)

All responses (8)

Answers (1)

Deenuji_Loganathan_ 6,250 Moderator on at

Like (0)

Report
Copy link

Link copied!

@SHLJV
I believe your described problem might resemble the situation outlined below. It's possible that in unattended mode, a popup dialogue could prompt for validation of your connection. Therefore, consider utilizing PowerShell scripts or alternative methods to capture hints, such as screenshots, once your system has booted. This approach may provide a clearer understanding of your issue.

New "Run Flow" Connectors Dialog Box Breaks Schedu... - Power Platform Community (microsoft.com)

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀. If you'd like to appreciate me, please write a LinkedIn recommendation 🙏

Was this reply helpful? Yes No
SHLJV 15 on at

Like (0)

Report
Copy link

Link copied!

@Deenuji
Thanks for the suggestion. I implemented the tips from your shared topic. Both your suggestions with the checkbox and the solution with running the application from with another flow. Unfortunately, it doesn't change the outcome. It runs great attended both when started from Desktop itself as from the cloud. But the moment I want to run it unattended, it errors.

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Moderator on at

Like (1)

Report
Copy link

Link copied!

@SHLJV
Ah got it. But Have you tried with create some PowerShell scripts when systems on taking screenshot it find out what is exactly happening in your flow?

In the meantime, Refer this thread and try to create account accordingly and see if it resolves your issue.
Solved: Access to some desktop flow connectors wasn't vali... - Power Platform Community (microsoft.com)

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀. If you'd like to appreciate me, please write a LinkedIn recommendation 🙏

Was this reply helpful? Yes No
SHLJV 15 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the help and suggestions so far! As for Powershell will try to play a bit with that.
As for the shared thread I had already tried this. Everything is already connected to the "robot" account. Unfortunately it doesn't help. It runs fine in attended mode and also all the other activities are running fine. It's just the combination of sharepoint activity in unnattended mode that produces this error.

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,250 Moderator on at

Like (0)

Report
Copy link

Link copied!

@SHLJV
Is this issue arising after upgrading your PAD version? A few weeks ago, someone mentioned that this occurred after upgrading to the new version.
If this is the case, you may consider to revert to that version for now and simultaneously raise this issue with Microsoft as well.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀. If you'd like to appreciate me, please write a LinkedIn recommendation 🙏

Was this reply helpful? Yes No
sergiopereira83 25 on at

Like (1)

Report
Copy link

Link copied!

Try creating a sharepoint connection reference in the same solution as your desktop flow and using it in the flow's sharepoint action.

Was this reply helpful? Yes No
Verified answer

Agnius Bartninkas Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

It might be a good idea to try and create the connection reference properly via the cloud portal instead of the desktop flow editor. Navigate to Solutions, create a new solution, and then add a connection reference there. You might also want to move the desktop flow and the related cloud flow to that solution (for proper backup if needed) via the "Add existing" menu.

If this doesn't help, I suggest creating a support ticket with MS.

Was this reply helpful? Yes No
SHLJV 15 on at

Like (0)

Report
Copy link

Link copied!

Indeed, this was the solution for me. All connections are with the "robot account" however, when I started off the unnattended flow I did it from my own account in make.powerautomate.com. When I logged off and logged in with the "robot account" in the cloud flow, the flow run succesfully.

Was this reply helpful? Yes No