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

Office 365 Outlook Connector repeatedly failing

I have a pair of flows that have been working well since April that, in the last two weeks, have started failing repeatedly.

 

The Office 365 Outlook connector keeps breaking, almost on a daily basis now. The error message is:

  • Error from token exchange: Runtime call was blocked because connection has error status: Enabled| Error, and office365 is in the block list. Connection errors: [ParameterName: token, Error: Code: Unauthorized, Message: 'Failed to refresh access token for service: office365certificate. Correlation Id=0b65906a-623c-481f-8e59-10fcbc170981, UTC TimeStamp=11/26/2018 2:12:47 PM, Error: No refresh token.']

On this occasion I had checked that it was working just an hour ago and broke in the intervening time.

 

I can correct the connection issue using the "fix connection" option, but this doesn't last. The example I've given is for a very simple flow:

2018-11-26, Flow outlook connector fail.png

1 ACCEPTED SOLUTION

Accepted Solutions

This issue is now resolved. I passed on all the details to system support and they finally got back to me last week to say it is working again. Microsoft seem to have done an update to flow as the error messages on the old failed flows have changed. My flows have now been working correctly for the last week.

View solution in original post

4 REPLIES 4
Community Support
Community Support

Hi @cmcbrien,

 

I afraid that the issue is caused by token lifetime.

 

Please refer to link below to learn more details about the token lifetime:

https://docs.microsoft.com/en-us/azure/active-directory/active-directory-configurable-token-lifetime...

 

 

Best regards,

Alice

Ah, that helps.

 

Looking at the document you linked, it seems likely that it is due to the LastPasswordChangeTimestamp attribute. I checked with my manager (it's his connectors the Flow uses) and he hadn't changed his password in some time which would match the sharply reduced token lifetime we have been experiencing.

 

He has changed is password now and reverified the connection. I'll check with him later today and tomorrow morning to confirm that the connector is still active.

 

Thanks for your help,

 

Charles

That didn't fix it; it still failed after an hour.

 

After some searching I discovered that, apparently, there are issues with Azure MFA implimentation messing up Flow connectors. See https://powerusers.microsoft.com/t5/General-Flow-Discussion/Flow-Connections-error-due-to-Credential... and a workaround (that I won't have access to) https://blog.peterdahl.net/2018/01/09/microsoft-flow-and-azure-conditional-access-azure-mfa/

 

Other users of Glow Scotland have been having the same issue over the last few weeks. So it looks like a system-wide fault. I'm about to try phoning up my organisation's system support to find out if there's a way I can report it up to Glow Scotland, but I've got a feeling my Flows are now broken for the forseeable future.

This issue is now resolved. I passed on all the details to system support and they finally got back to me last week to say it is working again. Microsoft seem to have done an update to flow as the error messages on the old failed flows have changed. My flows have now been working correctly for the last week.

View solution in original post

Helpful resources

Announcements
PP Bootcamp Carousel

Global Power Platform Bootcamp

Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.

secondImage

Power Platform Community Conference On Demand

Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Top Solution Authors
Top Kudoed Authors
Users online (11,710)