When you use connectors in Power Automate you may have seen broken connections.
Reasons for broken connections
Sometimes things have gone wrong within the connection and Flow will report this to you. I’m trying to collect the reasons and the how to fix the connection in this post. If you have found any other reasons feel free to leave a comment at the end of this post.
You might find that you get these blue Fix connection messages in your connections overview.
Most of these cases it is just a matter of clicking the fix connection link supply a password and then your connection will be marked as connected again.
You might also find that when you visit https://flow.microsoft.com you get the following message saying
We have found X of your connections in a disconnected stat. Would you like to fix them now?
And then you might even find many broken connections as shown below after I clicked on the Fix button. This is quite useful as you now only get the broken connection
Unlike earlier the connected connection are not listed in the fix overview but still this doesn’t look good!
Using FlowStudio you will also find all the broken connections.
And now when you right click on the broken connection and select connection JSON you will get the following
This connection is not authenticated
Failed to refresh access token for service
Failed to refresh access token for service means that you will need to supply your username and password again. The error message will supply you with what the connection cannot get an access token for. For different connectors you might get a slight variation of the message. for example the SharePoint connector will give you
I’m sure there will be more reasons for connections to be broken. When connections break it can make your system struggle. To help others please do leave your experiences in a comment below so that others can benefit from your lessons.
4 thoughts on “Broken connections in Power Automate”
I’ve seen two-factor authentication leading to broken connections in Flow, and the apparent solution was to use a service account that doesn’t have 2FA enabled.
Yes, I agree, for connections I would also use accounts that don’t have MFA enabled.
We have flows with this error that are started from power apps, so my understanding is that the connections are run using the user’s credentials, not the flow creators.
How do we handle this if the users need to fix their connections?
Hi Chad, just a quick idea. Maybe a flow could scan for broken connections and tell the users where to go to fix the connections via an email alert.