Reply
avatar user
Anonymous
Not applicable

Repeated error in the connector

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.

26 REPLIES 26
v-xida-msft
Community Support
Community Support

Hi @Anonymous,

 

Could you please share a screenshot of your issue?

 

The error message seems to tell that there is something wrong with the connections within your flow, the refresh token has expired due to inactivity within the connections of your flow. More details about the Refresh Token, please check the following article:

https://docs.microsoft.com/en-us/azure/active-directory/active-directory-configurable-token-lifetimes#refresh-tokens

 

I could not reproduce this issue on my side currently, please check if there is something wrong with the connections within your flow. Please also consider take a try to update the connection within your flow with the following article:

https://docs.microsoft.com/en-us/flow/add-manage-connections

 

In addition, you could also take a try to re-create a new connection to the connector within your flow and then try your flow again to check if the issue is solved. Also please clear cache of your browser and re-create your flow again to check if the issue is solved.

 

 

Best regards,

Kris

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
avatar user
Anonymous
Not applicable

In the end, I still did not know why I got that error, as I have reauthenticated connections and even created similar new ones.

I have also contacted ms flow support person, but they can't figure out what's wrong.

 

So what I did is I created a copy of that error flow, connected the powerapps to that duplicated flow and somehow it works. 

avatar user
Anonymous
Not applicable

Hi Kris,

 

That mean I need to constantly use the app, so the flow could work? And for how long can it be inactive before it expires?

spdevel
Advocate II
Advocate II

This error is occuring becuase you have MFA enabled on your tenant with a timeout sent on the token.  When the token expires, you will be required to re-authenticate any connections you have to O365.  If you setup a service account that does not have MFA enabled you can work around the issue until MS gets it fixed.  This is a known bug.

avatar user
Anonymous
Not applicable

I work with An and can confirm that we have no MFA implemented on this tenant. The process intermitantly fails and then succeeds and then fails, etc. This is a serious issue with MSFlow and makes me very nervous using it. If I cannot rely on the system to send an email I now need to look at alternative solutions for this and not use MSFlow for emailing. I wonder what other parts of the system will intermitantly error? Is the a listing of all of the known bugs to help us decide whether Flow is the right tool for each use case where we need workflows?

I agree with @Anonymous can someone from MS please address this issue?

 

@KentWeareMSFT

Dean Gross

Office 365- MSCA
SharePoint - MCSE
Microsoft 365 Enterprise Administrator Expert

Hey There Mark!

 

Would you please email me at Jolevesq@Microsoft.com with this information, i would like to get you connected to our engineering support team.

 

Thanks!

avatar user
Anonymous
Not applicable

Hello, we have the same error in our tenant. It happens sporadically for some users and consistently for others. 

Looking forward to updates on fixes for this error.

 

Thanks,

Silvana

avatar user
Anonymous
Not applicable

Having the same problems. In the same way I'm not using MFA on the account.

Same issue with me.

 

Works 9/10 times and then I get the error message on the 10th

 

Is there an ETA on the fix?

JesperSimonsen
Frequent Visitor

I am seen this too and I'm a little confused if I'm doing something wrong? 

I created an approval workflow in the pages library of a site for News, it works for me and a few other, but fails for others? 

 

How do I troubleshoot this and is there a workaround?

 

Error from token exchange: Runtime call was blocked because connection has error status: Enabled| Error, and sharepointonline is in the block list. Connection errors: [ParameterName: token, Error: Code: Unauthorized, Message: 'Failed to refresh access token for service: sharepointonlinecertificatev2. Correlation Id=88e5135c-4f18-43b2-8394-c2b13a373787, UTC TimeStamp=12/20/2018 2:47:13 PM, 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 2018-06-22T07:21:57.7847063Z and was inactive for 90.00:00:00.
Trace ID: 8ac369a8-f423-4417-bce8-2ee78c073400
Correlation ID: 65dad1a2-d313-42fa-badf-3c7e4b00f766
Timestamp: 2018-12-20 14:47:13Z']

 

 

Got the same error

avatar user
Anonymous
Not applicable

Hello - we found resolution for our scenario.

 

How we resolved:

  1.  User who is having issue: go to SharePoint online
  2.  Click on Flow > select the flow
  3. Click on edit connections located at very bottom of pop up
  4. We had a SharePoint and O365 connection and one of these had a red !.
  5. Clicked 3 ellipsis > clicked red ! and there was option to re-fresh connection

After following these steps, the user was able to run flows again.

 

For reference, this is the error msg we get: 
Error from token exchange: Runtime call was blocked because connection has error status: Enabled| Error, and sharepointonline is in the block list. Connection errors: [ParameterName: token, Error: Code: Unauthorized, Message: 'Failed to refresh access token for service: sharepointonlinecertificatev2. Correlation Id=906bc70d-67ee-469f-b09c-33dd8fcbf9fd, UTC TimeStamp=1/4/2019 5:11:27 PM, 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 2018-09-19T19:17:43.3595038Z and was inactive for 90.00:00:00.
Trace ID: d5b7982a-78f5-44bc-b813-88c6cbe33000
Correlation ID: f01d5f24-1423-42fa-ae15-cff5355de9c8
Timestamp: 2019-01-04 17:11:27Z']

 

The error comes up consistently.

 

Hope this helps someone else!

 

Silvana


@Anonymous wrote:

Hello - we found resolution for our scenario.

 

How we resolved:

  1.  User who is having issue: go to SharePoint online
  2.  Click on Flow > select the flow
  3. Click on edit connections located at very bottom of pop up
  4. We had a SharePoint and O365 connection and one of these had a red !.
  5. Clicked 3 ellipsis > clicked red ! and there was option to re-fresh connection

After following these steps, the user was able to run flows again.

 

For reference, this is the error msg we get: 
Error from token exchange: Runtime call was blocked because connection has error status: Enabled| Error, and sharepointonline is in the block list. Connection errors: [ParameterName: token, Error: Code: Unauthorized, Message: 'Failed to refresh access token for service: sharepointonlinecertificatev2. Correlation Id=906bc70d-67ee-469f-b09c-33dd8fcbf9fd, UTC TimeStamp=1/4/2019 5:11:27 PM, 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 2018-09-19T19:17:43.3595038Z and was inactive for 90.00:00:00.
Trace ID: d5b7982a-78f5-44bc-b813-88c6cbe33000
Correlation ID: f01d5f24-1423-42fa-ae15-cff5355de9c8
Timestamp: 2019-01-04 17:11:27Z']

 

The error comes up consistently.

 

Hope this helps someone else!

 

Silvana


We put in a support ticket with Microsoft due to this bug and were told it was by design and there was no way for the Flow to give any indication to the user that there's a broken (timed out) connection. The only guaranteed workaround is to add in a "run after" check on the first step in the Flow that uses the connection of that user - in our case the Get SharePoint Item step - to send them email if it fails with instructions to edit the connection and run it again. While it will do the job to let the user know I find it close to unacceptable that Microsoft's answer to the user having no idea the Flow failed being "by design." Seems that's the most common answer I get to clear bugs in their solutions. 

With this issue, I have to make updates to all our production Flows to add in that check into the first step(s) that use the user's connection and (obviously) add this into the design of future Flows.

avatar user
Anonymous
Not applicable

The fun of adding in error handeling wheen there is no error! I would seriously recommend the use of other tools wehre you can get away with it as Flow is a broken product that looks like it will take a few years for the MS team to get working properly. To have connection tokens that no one knows anything about that only require a refresh to make work again seems a bit ammaturish to me. But hey I've only got 30 years experience in IT. And it is great when the flow is built to tell you something happened and then it fails to tell you. It makes us look so stupid to the user community. "What do you mean our critical incident flow failed and thus we failed a governance check just because it lost connection to soemthing that has had no change?" We have had a situation where a child care centre had to close for a day purely due to Flow token issues. So wherever possilbe use tools other than Flow if you want to know that the workflow you built functions all the time. Otherwise revert back to paper based processes.

mshoseini
Frequent Visitor

Hello,

 

In some cases, it is because of changing the flow admin account password. You should reconnect or refresh your connection in the Power Automate connections section.

I experienced this same problem see below with edits. Not what I expected from this product.

 

    "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: aadcertificate. Correlation Id="#ID", UTC TimeStamp=5/18/2020 6:20:16 AM, Error: Failed to acquire token from AAD: {\"error\":\"invalid_grant\",\"error_description\":\"AADSTS50173: The provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '2020-04-17T13:37:16.9808446Z' and the TokensValidFrom date (before which tokens are not valid) for this user is '2020-05-04T17:42:53.0000000Z'.\\r\\nTrace ID: "#ID" \\r\\nCorrelation ID: 96e24ee3-ff2a-45b3-8212-4e05388ae187\\r\\nTimestamp: 2020-05-18 06:20:15Z\",\"error_codes\":[50173],\"timestamp\":\"2020-05-18 06:20:15Z\",\"trace_id\":\"72b21403-ca45-48a7-98b0-f796f7a05400\",\"correlation_id\":\"'#ID'\",\"error_uri\":\"https://login.windows.net/error?code=50173\"}']"

 

DNS4ever
Frequent Visitor

Same issue, dedicated service account, no MFA for this account. Error like this and happens randomly:

 

{
"status": 401,
"source": "https://power-te-northeurope-1.azurewebsites.net:443/tokens/europe-001/office365/<guid>/exchange",
"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: aadcertificate. Correlation Id=<guid>, UTC TimeStamp=12/14/2020 3:26:20 PM, Error: Failed to acquire token from AAD: {\"error\":\"interaction_required\",\"error_description\":\"AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '<guid>'.\\r\\nTrace ID: <guid>\\r\\nCorrelation ID: <guid>\\r\\nTimestamp: 2020-12-14 15:26:20Z\",\"error_codes\":[50076],\"timestamp\":\"2020-12-14 15:26:20Z\",\"trace_id\":\"<guid>\",\"correlation_id\":\"<guid>\",\"error_uri\":\"https://login.windows.net/error?code=50076\",\"suberror\":\"basic_action\",\"claims\":\"{\\\"access_..."}']"
}

 

P.S.: Of course you need to log in after I press reply, then landing on the homepage, my message discarded. Happend 3x additional times. Fun part!

I wish I could have given you 1,000 thumbs up.

avatar user

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,085)