This is currently working in previously built apps but we noticed yesterday we cannot associate a Flow with a button in PowerApps currently. I've built a test app simply with one button on the screen and created a simple Flow using PowerApps as the trigger and Send an email (V2) as the action. When tested in Flow it works correctly. It will NOT attach to the button in PowerApps though. The error it returns is "Failed during http send request". We have also tried other actions besides email in the test Flow and it still fails and fails for every user we've tested.
We have tried multiple Flows and multiple avenues to attach the Flow to the button and it fails every time. I've included screenshots to show the error.
Can confirm that this is an issue for us. Cannot attach flows to PowerApps anymore. Existing apps built same way work fine, but new apps we cannot associate a button to a flow.
Hi @bheglund ,
Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. The screenshot as below:
Please consider take a try to create a new flow from your PowerApps app as below:
rather than create your flow within MS Flow portal, then check if the issue is fixed.
If the issue still exists, please consider submit an assisted support ticket through the following link:
We tried the "Create a new flow" option inside the app and chose a template (PowerApps -> Send an email V2) and also tried to create from blank (Instant) with the same trigger and action and both gave the same "Failed during http send request" error.
Hi @bheglund ,
Currently, I could not reproduce your issue on my side. I would post this issue to my Product Team to track this issue. If this issue is solved, I would reply here.
I'm getting same thing. Sometimes it gives me the error, sometimes it connects. I need to "ask in powerapps" for variables and that 100% causes it to fail. Also change anything in the flow and it will fail.
old flows will load. I've created them inside and outside of the flow portal at least a dozen different ways.
I can confirm and tested this. The flow connection in PowerApps is now locked behind Plan 1/Plan 2. This is NOT a premium connector, Microsoft. WTF?
That is ridiculous! I noticed that a lot more connectors are marked as premium. I began using the sql connector because it was not a premium and now it is.