You’re offline. This is a read only version of the page.
39
We use Power Automate Desktop for a business critical flow. I am used to keeping all our software up to date and understand the logic behind regular updates.
Power Automate Desktop has been a bit of a Cinderella product and not well known. Therefore the community has been tolerant of product deficiencies and gaps. However the development team have been making steady progress and so we all happily update (not that I think there is a choice).
The 2.7 release has revealed the danger of this practice. First browser component broke, then we find at some point in the past there was an issue with updating the Firefox extension. Most of us will have discovered this when trying to fix the "Assume control of browse" problem. The obvious action is to remove and reinstall the PAD extension. Then you notice there are two extensions and assume this is a bug, but no two extensions for different versions. It does not occur to you that if you remove the extension you won't be able to reinstall it as it has been removed from the Firefox store and all the community links are broken.
We need a slow update stream for users with business critical flows.
In my case, the loss of this process is causing insurmountable issues. I am on a business trip to the Ecuadorean Amazon supporting a charity reforesting the Amazon. I have only one laptop with me so cannot fall back on an office full of equipment. This flow is critical to enabling the work to continue.
Power Automate Desktop is a brilliant collection of tools, however, as we come to depend on it Microsoft must recognise that a wild west approach, while making development faster, is not safe in the mainstream.
Share
Report
All responses (
Answers (
