Hi Michael,
yes I removed the flow calls. I work on alot of informal requests, in a manner that's unstructured so
it lends itself to start and stop activity - or just started.
It's not causing any blockers or issues but just mostly annoying in housekeeping when managing connections
and dependencies. When I created a new gateway (because the current one was not documented - in terms of
gateway recovery keys and it was over a year or two old) - I shifted all my connections to new ones that were named
in a standardized way, I started to uncover the connection issues.
I did go into the rabbit old of sharepoint connections and those that couldn't be renamed - I have a
separate thread on that one - but determined that the best route there is delete all the connections and then
create a new single one to remove all the duplicates (note that's ideal in like my case when you are developer, admin and
IT staff all in one).
I'm working with Microsoft on a support case for this so if we uncover something I'll update this thread.
Additionally we also ran across connections that were not able to be deleted - you would receive permission errors --
those are solved by just running the PowerShell using the powerapps Management include - that works great.
I suggested several wish list items during my call such as: being able to sort and filter on the Power automate lists.
There are some things I also wish would be in the admin console - such as connections - you can dump the list
with PowerShell and there are many that accumulate over time by user - and it seems that would be a good way to
help manage those.
Anyway
I'll keep everyone updated, thanks!
