This page has 0 threads | Add post

Blogs

Finding our blogs useful? Please consider helping us to share more!

The 5 worst things about Power Automate Part six of a six-part series of blogs
To try to show what developing Power Automate flows is like, we've created two blogs: one listing out its 5 best features, and one listing its 5 worst ones. This is the pessimistic one! The 5 worst things about Power Automate 1 - The clunky user interface 2 - Those expressions! 3- How much do you want to learn JSON? 4 - Everything takes longer than you might expect to learn 5 - You can not disable actions (this blog)

The 5 worst things about Power Automate

Part six of a six-part series of blogs

To try to show what developing Power Automate flows is like, we've created two blogs: one listing out its 5 best features, and one listing its 5 worst ones. This is the pessimistic one!

The 5 worst things about Power Automate
1 - The clunky user interface
2 - Those expressions!
3- How much do you want to learn JSON?
4 - Everything takes longer than you might expect to learn
5 - You can not disable actions (this blog)

Posted by Andy Brown on 29 October 2022

5 - You can not disable actions

After 4 general whinges, this is a very specific one. You can choose to turn off any flow:

You can choose this option to disable a flow. It's still there, you can still see and edit it, but it won't do anything.

But if you choose any action within a flow, you can't disable this:

There's no option to disable an action, so you have to delete it and then reinstate it if you need it later.

When you combine this with a very clunky facility for copying actions, it does make building flows harder than it should be.

Parts of this blog
The 5 worst things about Power Automate 1 - The clunky user interface 2 - Those expressions! 3- How much do you want to learn JSON? 4 - Everything takes longer than you might expect to learn 5 - You can not disable actions (this blog)