web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Failed to validate tok...
Power Automate
Answered

Failed to validate token Timebomb

(2) ShareShare
ReportReport
Posted on by 789 Moderator

For the love of all that is Holy, what is this timebomb that Microsoft has detonated in my 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): '5/2/2024 11:59:59 PM', Current time (UTC): '5/5/2024 1:52:21 PM'.

 

Action: Send HTTP request to SharePoint

Method: POST

Body: 

{
"__metadata": { "type": "SP.Data.WfAutoPopListItem"},
"StartAutoPop" : "false",                                          (A Yes/No column)
"Status" : "Running",                                               (A Choice column)
"Completed" : "2024-05-05T13:56:47.2540904Z",  (A Date/Time column)
"wfErrorLog" : ""                                                      (A Single Line of Text column)
}

 

Results:

{
  "status"400,
  "message""Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256\r\nFailed to validate token: IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '5/2/2024 11:59:59 PM', Current time (UTC): '5/5/2024 1:52:21 PM'.\r\n"
}

 

Categories:
I have the same question (0)
  • Nived_Nambiar Profile Picture
    18,136 Super User 2026 Season 1 on at

    Hi @GDSI 

     

    Just to confirm - are you updating column values in your sharepoint list ?

    Thanks & Regards,

    Nived N 🚀

    LinkedIn: Nived N's LinkedIn
    YouTube: Nived N's YouTube Channel
    Blog: Nived Nambiar's Blogs

    🔍 Found my answer helpful? Please consider marking it as the solution!
    Your appreciation keeps me motivated. Thank you! 🙌

     

  • Verified answer
    abc 123 Profile Picture
    789 Moderator on at

    It appears that the connection reference has "expired".

    I've created a new one and replaced the timebomb. 

     

    Why does it do this?

  • Verified answer
    abc 123 Profile Picture
    789 Moderator on at

    A Microsoft support tech had this to offer:

    "The connection key for open API flows expires every 390 days, and we do not automatically refresh the connection keys. Expired connection keys cause the flow run to fail."

     

    There is no warning, no way to see how soon something is going to expire, nor a notification that it has expired. This time bomb is absolutely unacceptable and unprofessional. But I'm not going to ask shocked or surprised and the lack of caring from the Interns at Microsoft. Shame on them, nonetheless.

  • automateUser Profile Picture
    4 on at
    I've notice this in our environment and it can be a real problem when there are multiple connector connections under the same account and they expire at different times. I wonder if this certificate expiration tied to the prompt that pops up when visiting the power automate "My flows" page:
     
    "{x number} of your connections need to be reauthenticated to avoid the following flows from failing. The most common cause is a password change or policy update from your org"
     
    note: not sure how the above msg is detecting the change(s)...since there has not been any password change and any obvious policy update -- so what constitutes a policy update related for this prompt?
     
    Depending on where the token expiration happens, it could fail at the beginning of the trigger action, in the middle, or the end of the power automate actions.
     
    Has anyone have any luck discovering other ways to mitigate this issue? or at least discovering when this expiration will happen for a flow connection?
     
     
  • EH-07050809-0 Profile Picture
    2 on at
    Just got this error. To fix it, I followed these steps:
    1. In "My flows", select the broken flow.
    2. Select 'Edit'.
    3. Open the broken step - just doing this seems to recreate the connection.
    4. Save the flow.
    5. Run the flow again.
    Good luck 😊
     
    And thanks to folks on this thread for your help. The help within the app was pretty poor - the instructions didn't match the elements I could see on my screen.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 594

#2
Valantis Profile Picture

Valantis 328

#3
David_MA Profile Picture

David_MA 281 Super User 2026 Season 1

Last 30 days Overall leaderboard