Solved! Go to Solution.
Have you tried any of the options in this thread?
Seems like different things worked for different people (not super helpful, of course) - but for someone at the end it was a requirement to reinstall PAD & the Gateway, and ensure that mapped network drives are being used.
I'm also going to tag @VJR in case they've seen something similar...
Thank you Rhia. Unfortunately, my issue is, I cannot even add Power automate desktop call to the cloud flow so no question of failing. Once i add the connection i cannot save flow and get the error shown in screenshot above.
Thank you for trying though. This is really weired issue. I did try to create new cloud flow and cannot add this action there either.
@VJR Yes, I do. and Yes , both cloud and desktop flow are in same environment.
Does it matter, what service account is used in gateway configuration?. (I have left that default i.e. pbiiegwservice account)
Machine on which gateway is configured is windows365 machine.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Join Priya Kodukula and the licensing team, super users and MVPs to find answers to your questions on Power Automate licensing.