You’re offline. This is a read only version of the page.
23
I must be missing something here, because on the face of it Power Automate looks like it should be very powerful. But each time I come to try and use it I fail. Now, I'm not what I would call a good developer, but after 30 years in tech, I hope I'm not an idiot. This afternoon I spent another unproductive two hours failing to compose a simple workflow. Something I could knock up in code but because I want it to be owned by non-developers and behind SSO, Automate makes sense.
I try to create a flow, except every time there's something wrong when trying to pass values between blocks or actually do anything useful with them. When I think I have it, I press save and get errors which prevent me from saving, and yet the errors can't be fixed because they make no sense. I ask Copilot what's wrong and it says there's nothing wrong, I give it the error message and it tells me nothing's wrong, then suddenly things that were apparently okay in the flow are now not okay, but unrelated to the things that were erroring before. Now I have new errors. Except these errors are for things that were automatically filled out when I created the flow, so how can they be bad parameters in the block?
For example, a Conditional block that errors, saying there's a problem with the input to the block, but Copilot disagrees. All the Conditional is doing is checking message body starts with a word.
I'm tired, I hate it when tools want to appear useful but because they can't explain themselves properly you have to know everything before you can know what's wrong.
I've been able to make some useful automations with it, but it has been a head-bashing effort every step of the way.
I don't have a background in programming but I've build some SharePoint Designer Workflows in the past.
This is both a)much more powerful and b)much less beginner-friendly. We are very lucky that there is so much help out there for working around the challenges and limitations of the system.
In regards to the Power Platform broadly, I think Microsoft basically failed at "no-code." To do anything worth your time, you will have to create an expression, write some code, or perform some power query against data. The current environment leads people to create applications and automations using terrible practices and without the proper considerations in place.
I'd like to see them create some learning path that allows you to select your platforms and brings you through a real world set of examples using all of its platforms (BI, Apps, Automate, etc...).
This forum is by far the best place to get accurate answers from people who really know what they're talking about.
I find that it helps to just aiming at collecting success stories. Start creating a flow, and quickly end up in a place where you can run it and it works. I have a friend who just started on the same path - he chose the method of teaching his skills as a booster for his learning path, because he believes he learns faster if he can articulate what it is that is being done, rather than just copying template flows and such. You can check him out on the link below if you are interested, and develop your skills in parallel with him 🙂
Wow, I thought I was the only one having issues. This is not my first rodeo, I have done some programming in Basic, C, a little VBA, a little Python and a lot of UNIX Shell. And as far as I'm concerned PA is a major time sync.
I finally get a flow to work and then it stops, and I get error messages. Nothing changed so why does it work infrequently.
My flow watches an Outlook mailbox and when it sees a new email it is supposed to send it to a SharePoint folder. The flows says it was successful but nothing get delivered????
Hi @Bob_dvb ,
Adding to the comment here and for support. As a super user and someone that was self-taught through trial and error, what I can tell you the most comment learning experience I typically see with Power Automate is when users have a specific automation in mind (that may or may not be complex) and that becomes their first automation and project in Power Automate.
Goes without saying, many of the "first projects" are advanced-to-extremely advanced experience level.
That said, my recommendation to really get into Power Automate is drop the "need" projects and learn the basics with common connections and triggers, such as when an email arrives, do actions with the attachments, subject, body, etc. Build lots of flows that you don't specifically need in your current demand. Those basic flows are the best way to learn and that foundation will help you solve your current world problems. There are a lot of common actions that will make you feel very comfortable with Power Automate. There are lots of videos, templates, books, and more. Don't give up.
I am certainly having lots of issues, but I'm also very new to Power Automate. My issue is, as mentioned in this post, this is supposed to be a no/low code solution to help people who aren't developers automate tasks. However, the finicky nature of creating a tree is so terrible it would frustrate all the users I have, also the debugging is difficult because the error messages make no sense and I can't find any help documentation to decipher what the heck the error messages are trying to state.
As a side note, I'm very frustrated that when I try to automate creating a Planner task in a Teams channel based off a trigger, I cannot update the Notes section. I THINK it's possible with an update ticket action, but why not on the creation action? That just seems silly. As I was writing this another thing bothered me, the only text input field I could find in the task creator was the Title field, which has a limit of 255 characters. This application knows that, why wouldn't it by default only grab the first 255 characters of whatever you fill into the title field as the input? While trying to fix JUST that piece, my whole flow broke and I couldn't figure out how it happened. An apply to each action showed up out of nowhere and it's so high up in my flow that if I try to delete it the majority of my flow goes with it...awesome
I am having an absolutely terrible time with this too. The error messages are nonsensical and Power Automate does not seem intended to work with CRUD operations of any complexity. A simple delete query based on a trigger in SQL could be written by a beginner with no SQL knowledge than the equivalent in Power Automate.
The error codes/error messages are basically worthless and the uneditable "code view" mocks the user.
A nice talk touching this topic:
Dylan Beattie – Life, Liberty, and Pursuit of APIness: The Secret of Happy Code
Hi @Bob_dvb ,
Learning Power Automate (or any new skill) is a journey with ups and downs. It's not a smooth, linear path.
You will experience periods of progress followed by plateaus or even temporary setbacks. This can be frustrating, but it's a normal part of learning.
A plateau is a period where you don't seem to be making progress, even though you're still putting in effort.
But keep going through the challenges and setbacks. Celebrate small wins and recognise your incremental progress to stay motivated. Understand that the learning curve is bumpy, and see obstacles as temporary, not permanent failures. With consistent practice and persistence, Power Automate may well eventually become "second nature".
Like others here, I have 30+ years in experience in tech but started my real learning journey with Power Automate only in 2021.
The Bumpy Learning Curve | LeanProductivity (sascha-kasper.com)
Ellis
____________________________________
My Blog Site
Share
Report
All responses (
Answers (
