'Failed during http send request' when re-adding Flow datasource

[mchien]

Since i modified my Flow, I had to re-add the datasource to get new parameters to show.

So I deleted the datasource, but when i try to get PowerApps to automatically re-connect the datasource, it gives shows this error

Using Fiddler4, i get a 500 error:

{"error":{"code":"InternalServerError","message":"Encountered internal server error. The tracking Id is 'af278631-d529-4a14-b5ed-af6a2c51af5d'."}}

I'm not too sure what's going on 

[mchien]

It turns out, my flow had a parameter set to "Apply for Each" block in Flow.

It didn't seem to like that.

[michalkoziol]

so you simply deleted "aply to each"? i need this segment in the flow to loop over all sharepoint items

[Anonymous]

I just ran into this issue when updating a flow of mine.
Surely the issue can't be that you are not able to use Apply to Each actions in a Flow when triggered via PowerApps.
There's no way for me to avoid using a Apply to Each action with a Send an HTTP Request to SharePoint inside the loop

[PVosEska]

What browser might you be using? I had the same problem in FireFox. When i switched to Chrome it was fine though, i could re-add it again.

[ANB]

Hello,

Even I faced the similar issue.  This might occur when the Flow is created by Person A and then Person A share the Flow to Person B and now Person B is co owner of Flow, however flow is still using the connection of person A.

If Person B wants to add the Flow to PowerApp, Person B have to make sure that all actions which is used into your Flow like Get my Profile, SharePoint etc. is using Person B's connection.

It worked for me...!!!

Thanks,

ANB

[Anonymous]

Well as a bit of an update the previous flow that was throwing the error for me has now started working. In the sense that I could all of a sudden add it back to PowerApps.

I was using two different accounts so the point ANB brought up might have been relevant. But I also didnt change any connections between the error appearing and dissapearing so I dunno. Overall a frustrating experience, glad it started working, but I wish I had better tools to track the actual underlying issue. Too many issues are answered with "Have you tried rebuilding the flow from scratch"

[DavesTechTips]

Hi @Anonymous 

I have seen this error before when there was something wrong with the schema in the flow response. I have also seen this when the schema has an array of Required properties.

Dawid van Heerden
Follow on Twitter: @davestechtips
Subscribe to YouTube: https://www.youtube.com/davestechtips?sub_confirmation=1
**If you found this reply helpful, please mark this as the answer to close the topic and make it easier to find for other people with similar questions.

[Anonymous]

I had this error message when transferring ownership of the App and Flow to Person B. To resolve, Person B made a copy of the Flow using Save As, there was a prompt for Person B to allow connection to their Approvals, Outlook365 and SharePoint. Next Person B added the copy of the Flow back to PowerApps and this worked for us :).

Originally Person B manually switched connections for each of the actions in the Flow, however we did not do this for Approvals action as their is no option to do so, hence why we initially received the error message as not all Actions in the Flow was switched over to Person B.

[VK2]

What solved problem for me:
Be sure, that you are logged in as user in all connections, you cannot do it from another account, unless you change all connections to your account.
That means -> same person who tries to add flow to power apps must be same person who is specified in ALL conections in the flow, otherwise you cannot perform action adding it. (Or there is not any connection reference in whole flow) (Later you can change all connection references, but for adding it, this is necessary)

They could at least tell us, where is the problem... :V nothing much says: Http request error 😕 
That worked for me.
Good luck guys