What is the root cause of this error in the PowerAutomate? Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256 Failed to validate token: IDX10249: X509SecurityKey validation failed

[EA_PrafulSoni]

I have created a manual trigger flow on a selected file in the document library. The flow was running fine but suddenly one day while running the flow I am getting the below error in the flow.

"
Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256
Failed to validate token: IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): 'System.DateTime', Current time (UTC): 'System.DateTime'.

"

As a solution, I simply created a copy of that flow and a new copy of that flow is working fine.

Also, I checked all the connections are fine and similar other flows are working fine.

Can anyone let me know that what is the root cause of this issue and why this occurs?

Please let me know if you need more information.

Thanks!

[KMac1980]

Did you ever figure out what was wrong here? I am experiencing the same issue.

[CCOCE]

I'm having the same issue. Did you end up resolving the problem?

[PsaEko]

I had the same error on my reoccurring flow, 

solution:

Save As > then turn new flow on > delete old flow

tada!

[EA_PrafulSoni]

As a quick solution I created a copy (Save As) of the flow and it worked.

As per the Microsoft support engineer this issue was raised because my flow user's connections were not updated.

If your connections are not up to date, then this issue can occur. Also, it is not fixed that it will affect all the flows created using the same account, and it is also different according to the flow types (Automated, scheduled, etc.).

Also, if your organisation's password policy affects the connections.

Solution

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[EA_PrafulSoni]

As a quick solution I created a copy (Save As) of the flow and it worked.

As per the Microsoft support engineer this issue was raised because my flow user's connections were not updated.

If your connections are not up to date, then this issue can occur. Also, it is not fixed that it will affect all the flows created using the same account, and it is also different according to the flow types (Automated, scheduled, etc.).

Also, if your organisation's password policy affects the connections.

Solution

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[EA_PrafulSoni · Accepted solution]

As a quick solution I created a copy (Save As) of the flow and it worked.

As per the Microsoft support engineer this issue was raised because my flow user's connections were not updated.

If your connections are not up to date, then this issue can occur. Also, it is not fixed that it will affect all the flows created using the same account, and it is also different according to the flow types (Automated, scheduled, etc.).

Also, if your organisation's password policy affects the connections.

Solution

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[EA_PrafulSoni]

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[EA_PrafulSoni]

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[EA_PrafulSoni]

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[mbala2]

I am facing the same issue. I have more than 40 flows that use the same connection and I do not wish to save as because the flow is also being tagged in another application. Wish we get a resolution instead of workaround.

[EA_PrafulSoni]

As a quick solution I created a copy (Save As) of the flow and it worked.

As per the Microsoft support engineer this issue was raised because my flow user's connections were not updated.

If your connections are not up to date, then this issue can occur. Also, it is not fixed that it will affect all the flows created using the same account, and it is also different according to the flow types (Automated, scheduled, etc.).

Also, if your organisation's password policy affects the connections.

Solution

So, simply do one trick that remove all the connections which is showing errors (Outlook, SharePoint etc) from the flow and re-add the connections, and it will work.

[mbala2]

It is not a quick solution when you have 45 flows that are failing due to this unidentified issue.😥

[vwyankee]

---

@mbala2 wrote:

It is not a quick solution when you have 45 flows that are failing due to this unidentified issue.😥

---

You're not kidding. I thought I found the answer going into Data->Connections and using the fix connection option as I had a number of them showing an issue, including SharePoint (already fixed before screen shot):

...but it didn't fix it. I'd put in an MS support ticket, but it's at the point I need to fix it ASAP with my production workflow. Of course it isn't an issue in my dev and QA environments...

[EA_PrafulSoni]

You can check in Azure if there is any policy assigned for the security.

[cpafford]

For this error, I opened my flow (in edit), then clicked save, then the next time it ran it worked. The only Flows affected for me were Run By User flows. I did not have to create copies or do anything with the connections, so it might be worth a try? 

[VD]

Suddenly I started facing the same issue, I just resaved the flow and it solves the issue.

is there any better solution or best practice? because I have more than 50 flows and I can't manually resaved all the flows.