I love a lot of things about Power Automate. It is a very quick way to get from idea to exceution. Used well, it can be very powerful. It is not the solution for everything, and probably shouldn’t be used for some things, especially transactional things where rollback may be needed. But it is definitely a strong product overall.
That said, there is a bit of clunkiness to a few things. I am going to list some of the most frustrating problems that annoy me a little, and maybe write some posts going into more detail, and offering some workarounds that I have come up with after putting in the effort.
- Having to add “&v3=false” to the end of the URL in the maker portal to be able to use a useable designer
- New connection references being generated within a cloud flow for the same connector that already has one
- Copy and paste for flow steps still being in preview, despite being released in ..??
- Only having one level of variable in a cloud flow
- Being unable to easily filter flow history by information from the trigger
- That bug where if you have added or moved steps around in a cloud flow, it loses track of where everything is and you have to save and then refresh the designer before trying again
- Hidden throttling limits
- Bugs with boolean vs text
- Null handling being very inconsistent
- Inconsistent load times of command bar
- Limitations with switch statements
- Limitations with changesets

Leave a comment