Showing results for 
Search instead for 
Did you mean: 
Helper I
Helper I

"x-ms-failure-cause" : "apihub-token-exchange",

I'm integrating my personal app with Microsoft Flow.

When I try to receive a file content (example: Flow that creates a new document inr my app storage everytime a file is added to OneDrive) it retrives this error:

"x-ms-failure-cause": "apihub-token-exchange"Capture.PNG


 What am I doing wrong?

Community Support
Community Support

Hi Fvamaro,


You said that you are integrating your personal app with Microsoft Flow, so which app are you using?

How is your flow configured?

Could you show me a screenshot for your flow to help reproduce this issue on my side?

Best regards,
Mabel Mao

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-yamao-msft

There you have my flow:


However, when an email is flagged, Flow returns the error:Att2.PNG














I have exactly the same issue. From my Flow I am using my custom connector to make an API call. Testing within the connector works just fine without any errors using the same connection as configured in the Flow. But when the Flow is running I get this Bad Request with the same error. Very curious what's going on and to solve it.




@Octavie are you working with files too?

No, not working with OneDrive files or so. I have developed an Azure Web API, that needs to be called from the Flow. For that, I needed to create a custom connector.




I very much followed this article: 



Somehow I keep thinking it's about the account that I use for the connection. I have a dedicated service account for this, while I am editing the Flow using my own account. Maybe I need to investigate this more...


I'll keep you posted.



@Octavie I'm using 2 different accounts too.


Wow. Just wow. How misleading is this error message. It seems my API does get called, because I see my logging information show up in Application Insights (Azure service). At some point it has logged a 403 forbidden exception, which means my service account is missing some permissions 🙂 #AlmostGotMyNeedleInTheHaystack




Solved it. So, in my case it was the missing Permission piece. Once I set the required permissions for the service account I used in the connection, the Flow finished successfully. 🙂 I do hope you can solve yours as well very soon!




What have you done to solve it? @Octavie

@FvamaroFrom your custom connector, when you go to the Test tab, can you successfully execute your action from there using the same connection you are using in the Flow?




No, retrives error 500 @Octavie

So, 500 means, you can connect, authentication goes fine, but executing some code (?) within that component fails. It throws the InternalServerException.... You need to debug it more to find your needle. Keep testing it from the connector, before using the complete Flow...

Good luck!



Helpful resources

Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

Users online (4,340)