I have created a Flow to get items from Sharepoint with a PowerApps trigger. The Flow selects items and adds them to an HTML table. It then emails the table.
When I try to add the Flow as an action in PowerApps it gives me the error message 'Failed during http send request'.
I have tested the Flow and it is working, so I cannot see where the problem is in PowerApps.
So here you mean the Flow added under PowerApps would show "'Failed during http send request" after pressing the trigger within PowerApps?
Testing the Flow under PowerApps and it works from my side.
If it is convenient, please try to reproduce this issue, once issue reproduced, please copy the Session ID under PowerApps and paste it here, I will then forward this to the proper team to take a further look.
Session ID could found under:
No, the flow is working when I run it from within Flow, but I cannot add the flow to PowerApps due to the error message stated.
Referencing this discussion, I saw that there is a bug using the "Apply for Each" block in Flow.
My Flow did NOT have an Apply for Each block, however there was one automatically created which I later deleted. It appears that the bug remains even after removing the block.
I have reproduced the Flow making sure that there was not an "Apply for Each" block and I can successfully add it into PowerApps.
Ran into a similar issue.
I am able to reach the "Apply to each" but it crashes on the first SharePoint connector with some strange not related error. When testing the flow without PowerApps it works perfectly fine.
So to conclude: there is no way to have a Flow iterate on SharePoint connectors when starting a flow from PowerApps.
This is very disappointing.
AGREED - this bug IS alive & well in May 2018 !!!
For ME, this is so far exclusively related to the (AGGRAVATING) SendPushNotification.run() built-in action >;-(
- this action is SO dang fragile, you can only define if ONCE, and then it's like you CAN'T change it all ALL !
- also this action DOES let you parametrize the "Message" property - that functionality has never been a problem.
- what HAS been a problem is parametrizing the RECIPIENT property 😮
-- the syntax is SO dang ODD for even a single recipient, then trying to update the flow is SO unintuitive.
- so when I tried to 1)delete and then 2)re-add the app... THEN this bizarre "failed during http send request" appears !
PLEASE don't reply that I have to RE-BUILD the Flow from scratch - I WILL scream (and then cry pathetically) .
I just had this error the first time. Other flows add fine. This is brand new. I did a "save as" and the coped one does it too. This is so simple. It worked previously. I edited a "scheme", then removed/added back. It gave error when adding back.
If I delete the Response action, it will add. If I add it back in fresh, it fails again. I even tried in a fresh app. What can be so wrong with this Response action?
Have had this problem in some flows for 2 years now.
Workaround is to call a parent flow from Powerapps, and then pass the information from powerapps to a child flow.
Have seen the problem with both PowerApps v1 and V2 triggers.
Sad to still see this error in 2022.
Keep up to date with current events and community announcements in the Power Apps community.
Join us in Las Vegas to experience community, incredible learning opportunities, and connections that will help grow skills, know-how, and more.
Check out the latest Community Blog from the community!