cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
wnzn
Advocate IV
Advocate IV

Error 520 - API Hub token exchange internal server failure.

A flow in our environment is reporting the following error message:

"There's a problem with the flow's trigger."

 

Digging into the details gives the following:

{ "Message": "API Hub token exchange internal server failure.", "SourceUri": "https://power-te-northeurope-2.azurewebsites.net/tokens/*<shortened>*/exchange", "IsCachedResponse": "false" }

 

Refreshing the connection does not make it go away. I copied the flow and use that (that works) but this is not a reliable solution.

 

I noticed a number of similar posts here and I contacted support but I want to get the message out there that these issues still occur.

22 REPLIES 22
Brice235i
Skilled Sharer
Skilled Sharer

Just had an update on the premiere support ticket I raised: 

"our PG team we have asked the  SharePoint team to look into the issue as the clientRequestId for the trigger where PG seeing sharePointAdapterException is causing the issue and need their intervention to fix this."

I haven't read all the posts on this thread (there are so many!), but here is the info I got from my talk with Microsoft support today and my related thoughts:

  1. Microsoft says there is a known issue where authorization token on a data connection over the gateway can become corrupted.  Engineers are aware and working on it.
  2. Microsoft suggests two temporary workarounds for recovery.  My preferred solution is to recreate the connection and change the flows to use the new connection.  The message to fix the trigger does not go away until the flow executes the next time.  The other solution is to copy the flow (save as).  Personally, I don't want a collection of broken flows and a challenge figuring out which are the working ones.
  3. There is still an issue in discovering that the issue exists in a timely manner.  No email notice is sent because the flow never executes due to the trigger problem.  If I happen to notice that something didn't happen that should have, I can go into the run history and see if the fix trigger message exists.  Unfortunately, that is too late to recover in time for the dependent processes to work.  My idea is to create a heartbeat solution.  Schedule a flow to create a file over the same connection, which should fail and send a notice.  If I find that it does not, I can create a 2nd flow to watch for that created file, and send email if it does not find it.  

 

arkumar
Regular Visitor

I'm also getting this exception intermittently. Is there a resolution for this?

Helpful resources

Announcements
Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

V3_PVA CAmpaign Carousel.png

Community Challenge - Giveaways!

Participate in the Power Virtual Agents Community Challenge

Carousel 2021 Release Wave 2 Plan 768x460.jpg

2021 Release Wave 2 Plan

Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.

Users online (2,392)