Repeated error in the connector

[Anonymous]

Hello,

I have been having this repated error in my flow with this error message: 

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.

Error: Failed to acquire token from AAD: AADSTS70002: Error validating credentials. AADSTS70008: The refresh token has expired due to inactivity. The token was issued on 2017-09-21T00:00:13.7564950Z and was inactive for 90.00:00:00. 

All my connections are connected. Can you suggest the next step I should take to resolve this error?

Thank you so much.

[aniket_shinde]

I have similar one but the error is Error: Failed to acquire token from AAD: {\"error\":\"invalid_grant\",
\"error_description\":\"AADSTS135011: Device used during the authentication is disabled. Can someone tell me a solution for this?

[dhock]

Using a service account without MFA is definitely not the solution when it comes to a flow with a Power Apps trigger, since the flow will run using the user's credentials. We have a flow that runs when the user accesses the Power App to see if they are in a particular SharePoint group (for controlling what they can do in the app), and we're still experiencing a lot of failures with it. If the user tries a second time, it usually works, but it doesn't look good for us when we have to tell our users to do that.

[PhilD]

Same issue here... randomly fails but cannot consistently reproduce the behavior. Agree with not using this product if you have any other alternatives.

[Guz_90]

I just experienced the same problem, is difficult to believe that is not possible send emails in a reliable way using flows. I have to send remainders weekly to some users is there any work around for this or plan to fix it from Ms side? The fact that somebody said that Ms told them in 2019 that this is done by design is disturbing  

[zayarminaye]

I am having same issue like Anonymous.  In my case, user was at home by the time using the Power app (in which instance email sending flow was integrated upon completing the particular patch function). In my flow, the connection account in Outlook email action is the service account. 

And I did some research about it and they said that it must be the reason of Conditional Access Policy in Azure AD which restricted the users from using some of Azure services based on the inbound connection.

Is it because of this or something else? 

Please request your support on solving this issue for good. Much appreciated.

Best Regards,

Zayar

[osflake]

Any solutions from MS Team?

[mlavender]

I just had this behavior happened and found this thread. I was in the middle of updating a flow and the error popped up. Of course I lost all the updates I did because I could not save before exiting to go refresh the connections. This happens at random and its very inconvenient. Sigh!