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

Flow Lifetime validation failed

Hi all, we have designed a flow, tested and it worked like a charm!

 

Basically, it works as an approval process, that forwards to the next agent upon approval, and so on. It does have from 3-5 approvals (depending of the case).

However, we are encountering some problems, some of the runs are reporting problems when the approver actually perform an action on it (when he hit either the Approve or Reject button at the message), it returns:

 

ActionFailed. An action failed. No dependent actions succeeded.
 
And just this week, when we had this new update on the Flow layout (where it shows a left-side menu with the error details), I was able to see the following:
 
{"Message":"Error from ASE:Bad key authorization token: Failed to validate token: IDX10223: Lifetime validation failed. The token is expired.\nValidTo: '05/30/2017 21:29:09'\nCurrent time: '05/30/2017 23:40:29'."}
 
So, when a token is generated (Response Approval Email, from Office 365 service) and one of the approvers takes a long time, does that token expire? Can we set a period for this token? Is there any workaround for this case?
 
thank you,
Allan
1 ACCEPTED SOLUTION

Accepted Solutions
TravisB
Power Automate
Power Automate

Hi @AllanMartins,

 

We are aware of this issue and are looking into a fix.

 

This happens on manually triggered flows. For security reasons we limit the period that the access token is live, and that's currently set to 1 hour. This period has been generally fine for most use cases until now, but new scenarios around approvals are broken by this.

 

In the next month or so, the limit is going to be raised to 7 days. This should help out the majority of cases trying to trigger approvals with manual triggers.

 

Thanks,

Travis

View solution in original post

48 REPLIES 48
TravisB
Power Automate
Power Automate

Hi @AllanMartins,

 

We are aware of this issue and are looking into a fix.

 

This happens on manually triggered flows. For security reasons we limit the period that the access token is live, and that's currently set to 1 hour. This period has been generally fine for most use cases until now, but new scenarios around approvals are broken by this.

 

In the next month or so, the limit is going to be raised to 7 days. This should help out the majority of cases trying to trigger approvals with manual triggers.

 

Thanks,

Travis

Hi @TravisB

 

Thanks for the reply on this. Looking forward to see this period extended. Will there be any announcement, or should I check in the next weeks?

 

We have a really good use for the Flow (in combination with others services) and this feature would be crucial to get it

to work.

 

Thanks!

Just marked your reply as the accepted solution! thanks

I can go ahead and bump this thread when the change is deployed.

 

This is a security change though and needs thorough vetting before release, so a fix is going to be several weeks out.

 

Thanks for reporting this issue!

 

Best,

Travis

I can go ahead and bump this thread when the change is deployed.

This is a security change though and needs thorough vetting before release, so a fix is going to be several weeks out.

Thanks for reporting this issue!

Best,
Travis

TravisB,

 

just to make sure I understand he issue; yesterday afternoon, I've created a button flow assigning an approval to a user.

This afternoon (so after 22 hours), the user approved the task; no lifetime validation error; does that mean the fix has been deployed ? 

Hi @sergeluca, quick question...

 

Have you done it using the Approvals service, or a O365-Approval Message?

 

I noticed that Approvals can manage it without major problems, but I see some cons with this service, in comparison with the O365 one:

- no support for Rich Text/HTML on the Body

- force the approval to be a "two-step" process (Approval respond on the message, then opens a page - where he is prompted to add a note - and then he submit his respond)

- cannot delegate an Approval

 

Approvals service is nice, but those 3 items is a problem for our use, so we decided to move with the O365 one for now.

 

regards, and thank you for adding a comment on this subject.

Allan

Hi Allan,

 

Thanks for the feedback. We are adding the ability to delegate approvals within the next month and adding support for rich-text/HTML is on our backlog also, slated for a little later in the year. Could you please elaborate on why the "two-step" process is problematic? We designed a two-step process so that approvers had an opportunity to make a comment on why they either approved or rejected a particular request. 

 

Thanks,

Merwan

Hi @sergeluca,

 

That is a good point!

 

It's complicated from the implementation side, but the long-short of it is that the approvals themselves will work, but after an hour attempting to call into any other connections will start to fail.

 

Also just got word on the fix - looks like one's ready and should be out globally by the end of next week.

 

Thanks,

Travis

Hey, just realized that I didnt phrase it properly... The two-step approvals has some benefits too!

 

But as more we go with it, there is always more need to make it more flexible, e.g: In our scenario, we would like to have the ability to "just" Approve (click once, and it's done - no need to "click again"), and to "Reject With comments" (so an approver would reject and write the reason why he is rejecting.

 

I think that a way to let the user/dev set this up for matching different scenarios, it would add (even more) value to the tool. Overall, the service is great!! It works fine, looking forward to see the new feats coming out. We are making a massive use of the Flow/PowerApps/Sharepoint combination and we have a great experience, other than the "token timeout" (which is forcing me to manually retrigger flows with expired tokens) I see endless ways to use it - and I can see way more to go with 🙂 .

Anonymous
Not applicable

Hi all,

 

Wondering if there's any official word of a fix being rolled out for this issue?

 

As of this afternoon we're still getting the same issue. A lot of people are starting to lose faith in Flow when they are forced re submit forms if their manager hasn't responded to it after an hour.

 

Cheers

Hi @Anonymous,

 

The fix should be available globally now.

 

Can you see if you're still seeing the issue? If so, we'll need to investigate.

 

Thanks,

Travis

Hi @TravisB

 

I just triggered some flow now, will wait few hours to check if the token for the response are now updated. I keep you posted.

 

I assume that we dont need to redesign the flow, or whatsover, correct?

 

thanks,

So, here is the result... it didnt work (at least for an existing Flow)...

 

Flow triggered at 19:54 UTC (or 16:54, GMT -3, which is my local time)

 

expired token.PNG

 

Do I have to redesign the flow?

Hi @AllanMartins,

 

No, I don't think recreating your flow will help. We are seeing the same thing on our side with old flows, at least.

 

I'm working with the folks who made the fix to see what's going on here. I'll update this thread with any news.

 

Thank you for letting us know about this!

 

Thanks,

Travis

Anonymous
Not applicable

Have just tested and the same issue seems to be persistent here. Error message same as @AllanMartins above.

 

Let me test if a new flow is affected the same way...

 

Edit:

 

Looks like new flows are being affected in the same manner. I created a new one this afternoon and waited 2 hours to respond to an approval prompt and received the same authentication error.

 

{"Message":"Error from ASE:Bad key authorization token: Failed to validate token: IDX10223: Lifetime validation failed. The token is expired.\nValidTo: '06/20/2017 03:03:12'\nCurrent time: '06/20/2017 04:18:54'."}

I also have big issues with this! Glad that it's currently being looked up asap.

 

EDIT; It failed sometime between 1 hr to 2 hr, clearly the update that prolongs the flow lifetime isn't working.

 

One of n numbers of objects; Fault msg

 

[quote]{"Message":"Error from ASE:Bad key authorization token: Failed to validate token: IDX10223: Lifetime validation failed. The token is expired.\nValidTo: '06/20/2017 07:57:52'\nCurrent time: '06/20/2017 08:02:52'."}[/quote]

I thought I would add more information about my case;

 

Flow;

SQL Server -> Common Data Service

 

2413 objects

 

1 hours nets me around 1200 - 1500 objects. So I need the flow going on between 2-3 hours to complete the flow.

There was a miscommunication - sorry for getting everyone's hopes up :x

 

The change to extend the lifetime of these tokens is actually rolling out with the current deployment and should be available globally by mid-next week.

 

We appreciate everyone's patience as the change rolls out in cadence with our safe-deployment standards

 

Thanks,

Travis

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 (5,596)