Error from token exchange - bad Key authorization token in Power Automate

Instantly Solved: Error from token exchange: Bad Key authorization token in Power Automate – Microsoft 365

No comments

 720 total views,  5 views today

Error from token exchange in Power Automate – sometimes we might notice that all of a sudden our working Power Automate has stopped triggering and if we look at the error details from the flow run history, we will see the below error:

Troubleshooting Steps when Salesfor...
Troubleshooting Steps when Salesforce is Down
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: '07/07/2022 17:37:45' Current time: '07/16/2012 23:19:27'. 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."

Fix or solution: Error from token exchange in Power Automate

By looking at the error don’t panic, the error message says something, but the actual is different. In the Power Automate SharePoint connection has been corrupted, for this either we need to delete the SharePoint connection and re-add back or export the faulty Power Automate in the zip file and import back the same exported file and rename the flow – here automatically your SharePoint data connection issue will be fixed and the flow or Power Automate will start triggering or working as usual.

That’s it, the issue will be resolved. 🙂

Summary: Error from token exchange in Power Automate

Thus, in this Power Automate troubleshooting article, we have learned how to fix the “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: ’07/07/2022 17:37:45′ Current time: ’07/16/2012 23:19:27′. 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.”

See Also: Power Automate Tutorial

You may also like the below Power Automate tutorials:

 

About Post Author

Do you have a better solution or question on this topic? Please leave a comment