Flow Lifetime validation failed

[AllanMartins]

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

[TravisB]

Hi @AllanMartins,

Glad to hear it! Think it was just deployment timing weirdness that you were seeing.

If you start to notice issues resurface, please let us know!

We appreciate your patience while we rolled out the fix!

Thanks,

Travis

[sergeluca]

TravisB, just to make sure I fully understand :

-1 approval can take max 7 days (new build)

-The flow lifetime can be max 30 days according to the documentation : https://flow.microsoft.com/en-us/documentation/limits-and-config/

Is that correct ?

Can the MS Flow documentation be updated with this ?

[TravisB]

Hi @sergeluca,

It looks like the approval scenario was also updated to have a token lifetime of 30 days.

Thanks,

Travis

[Justin_Reading]

This issue has just occured with us today. One of our global admins activated a Plan Flow 2 trial and all of a sudden our existing Flows are erroring out.

Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256 Failed to validate token: IDX10223: Lifetime validation failed. The token is expired. ValidTo: '04/03/2018 01:31:21' Current time: '05/08/2018 05:14:56'. bad token. Error=The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.

The Flows in question are monitoring changes to Dropbox folders online. Has anyone else experienced this issue?

[ghrimm]

---

@Justin_Reading wrote:

This issue has just occured with us today. One of our global admins activated a Plan Flow 2 trial and all of a sudden our existing Flows are erroring out.

Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256 Failed to validate token: IDX10223: Lifetime validation failed. The token is expired. ValidTo: '04/03/2018 01:31:21' Current time: '05/08/2018 05:14:56'. bad token. Error=The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.

The Flows in question are monitoring changes to Dropbox folders online. Has anyone else experienced this issue?

---

This is also happening to me after I re-submitted a failed run. Shouldn't the token have been refreshed when I resubmitted the run? It failed on a step where it was trying to access the on-prem database using a SQL Server connector and it shows that the connector is connected.

The initial failed run was started on Jun 21, 9:47 AM and it failed on 2018-07-04 18:43:21Z when the Approval email was actioned on (13 days). This is clearly less than the 30 days mentioned in https://docs.microsoft.com/en-us/flow/limits-and-config before pending Approval expires. The Flow was initially triggered via a PowerApps button. Are the token expirations between a PowerApps-triggered Flow and Flows triggered with a Flow button different?

[Anonymous]

Hi @TravisB 

I have just started getting this message too.

It was just after I added the following code to Set Variable 5

concat(substring(variables('FirstName'),0,1),variables('LastName'))

[DTreg1]

Hi @TravisB 

I started receiving this error a couple days ago, I thought it was related to something else so I tried to troubleshoot it but no luck.

Can you please help me with this?

[DTreg1]

Nevermind, I figured out the issue, because the record I was trying to update had changed primary keys, I needed to adjust back to the old primary key.

[Anonymous]

Hi,

Receiving the same errors on a standard template "When a file is added, approve file using SharePoint Content Approval".

My Content Approval is on