I am adding my flow to my powerapps but I encountered this error. I already tried running it manually on the flow and it did not return any error and it was successfully completed. I tried adding this flow on other app but I still got the same error
Could you please share screenshots of Flow configuration?
This document is about how to add a Flow in the PowerApps, you can follow it to confirm steps are correct.
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I am receiving this same issue. I followed the instructions provided, substituting a Common Data Service (Current Environment) action for the SharePoint example action. The flow runs fine when I test it, but I cannot add it to my canvas app. This is minimum configuration, which tells me this as an issue with the PowerApps/Automate connectors, not my setup.
I found a workaround for this. Create a new flow with the PowerApps trigger and a built-in action, i.e. something that doesn't require a connector. Save the flow, and open up the canvas app editor. The app should now be able to load the flow without issue. Save the canvas app, and return to the flow editor. Add additional connectors/actions to the flow and save. Now, the canvas app should be able to successfully trigger the full flow.
This is a pretty simple workaround if you are creating a new flow, but might be a real pain if you're trying to add an existing one to your canvas app. I haven't confirmed what happens if you have to change your flow's input schema after adding it to your canvas app, so plan ahead and define those with the initial flow creation if you can.
The issue here is that my flow exceeds the limit of actions per flow. Currently, Microsoft is allowing only 250 actions per flow. The error shown on the powerapps is quite vague which had me 2 working days before we figure out what causes it.
Is the microsoft account that made the flow the same as the one that is making the app? I got exactly this same error trying to use a flow that a colleague made. It worked after I shared the app with him and he added the flow to powerapps with no problems.
Yes it is the same account. I am the creator of the PowerApps application and the creator of the flow. I have attached flows many times. Something has changed, probably has to do with the licensing scheme since today I got a notice that my free trial had ended, which was very surprising to me since I am using a license through the company that employs me. Everything works, I just cannot attach a new flow to a PowerApps button.
I have asked the IT dept. about our licensing.
We observed that when the flow is not shared to person who is going to use it on apps, it will not show or will not work. But when we shared the flow to that person, he eventually able to connect the flow on apps. That's one thing we need to remember when connecting flows to our apps.
@jbenetti - It turns out that we have exceeded 250 actions before when i posted this issue. Probably flows that are connected to PowerApps needs to have a maximum of 250 actions while flows that are not connected to PowerApps can handle 500 actions. You can check the number of actions you have on your flow using this link: https://flowstudio.app/flows
@karl_oliverioThanks for your input but I cannot even attach a flow to a PowerApps button that simply asks for three variables. I have created a flow, form within powerapps using the 'action' tab. All my flow does in initialize three variables and then set the variables with ask_in_powerapps and it fails with the HTTP send request failed.
I have done this many times before, so something is broken and I suspect it has to do with licensing. But PowerApps and powerautomate are included in a business subscription to Office365. This is a pretty good size company so I doubt they went for a cheap solution. Like I say, it was working but now it is not.
I will probably move away from flows triggered by PowerApps, sometimes it's a lot easier to work with the flow, but this is clearly not easy anymore.
The error is useless and confusing, so I can only provide speculation.
But I believe a reason for this error is that the data-type that the flow requests is not supported. E.g. selecting "ask in powerapps" in the input field for an array variable may induce this error. I believe the supported data-types is described somewhere, but its not so obvious.
Its not so easy to update the data-type, this seems to happen with power-apps "automagic" when you click "ask in powerapps". I suggest selecting peek code at the PowerApps trigger, where you can see what datatypes the inputs have. I have often been forced to delete the trigger and ask all the questions again to repair it. I have found that the best way to deal with this issue is to initialize variables for all the questions at the top of the flow, that way its easier to re-build the trigger when it happens.
@hjaf Ok, that actually makes sense. I didn't realize that I couldn't pass an array to powerautomate flows. I will try attaching the flow without asking PowerApps for the array contents. I should be able to initialize the variable and build it in the flow. I do always put my variable right at the start of the flow, so that isn't the problem.
Thanks a lot for your input, I will post my findings when I get a chance to look at my problem again.
I usually just send arrays as a comma and/or semicolon separated string to flow and then use split(item(), ',') in a Select. If I want to have a 2 or more column array, I put split(PowerAppsString, ';') as input to the Select and each field with first(split(item(), ',')) and last(split(item(), ',')). I think you can get more fields from a string into an array with something like last(take(split(item(),','), N) etc but I haven't tried it. There are probably more elegant ways to deal with this, but it works 🙂
I have the same issue when I try to link Powerapps to any flow, even the simple one with only one step (initialize variable).
I don't understand why I have this error I already tried some of the workarounds sugested in this forum with no success. Please help.
Here is the Peek Code of Powerapps trigger in flow. Is there a possiblity that this error is related with the (,) instead of (;) ?
@joao123 is the variable you try to initialize an array? I see that the schema says object, but I don't think its possible to send an object. I think string or number are the only types supported at the moment. There are tricks to send arrays, but you have to do some translation on both ends to turn it into a string and back again in flow.
I'm not sure, but I think that when/if they implement a newer version of Odata its going to allow for more types.
The code that I post is the code of the trigger of Powerapps.
When I add a step to initialize a String variable and ask the values to powerapps the code take this form.
Anyway, I already try diferent types of flow templates, like the "send email" and still it shows the same error : Failed during HTTP send Request .
I am having the same issue connecting a Flow to a PowerApps button. In my case I am customizing a list form rather than creating a canvas app. Everything worked fine until I exported and imported the Flow so it would operate under a service account rather than my account. I imported it as New rather than Update.
The Flow (Send Email to Vendor) is now created and owned by SC1. SC1 is an SCA on the SP site
Send E-mail to Vendor is shared with me (WCC) plus some other admins
Send E-mail to Vendor was created as a Flow to be called by PowerApps button with no pre-defined actions.
I recreated Send E-mail to Vendor while logged in as SC1 and I still get the "Failed during http send request" error.
I did not create the Flow by selecting the "Create a new flow" option within PowerApps if that makes any difference.
Here is the code behind from the trigger:
"description": "Enter initial value",
"description": "Enter initial value",
Any suggestions wold be greatly appreciated,
Watch Microsoft Business Applications Summit sessions on-demand.
The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Automate Community!
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!
The top training and networking event across the globe for Microsoft Business Applications