Microsoft Teams resource connector token expired

💬 App Building
,
1
  • Goal: Use MS Teams resource to post Teams messages. It used to work but it's no longer working and I am getting this error for all of my Teams connected resource.
{
  "error": {
    "code": "InvalidAuthenticationToken",
    "message": "Lifetime validation failed, the token is expired.",
    "innerError": {
      "date": "2025-04-12T23:35:26",
      "request-id": "2dafab46-09e7-46d7-ae2f-39b2ced36b25",
      "client-request-id": "2dafab46-09e7-46d7-ae2f-39b2ced36b25"
    }
  }
}

  • Steps: I've looked into my own Azure instance but have not found the ability to refresh the token, I'm wondering if this is something on Retool's end? If not, please let me know how I can resolve this. This issue is blocking many of my services.

  • Screenshots:

CleanShot 2025-04-12 at 13.40.06@2x
CleanShot 2025-04-12 at 13.40.06@2x994×1484 89.8 KB

2 Likes
3

Bumping this again. We had the same issue occur on Friday/Saturday at some point. I was able to send through an OAuth request as the intended service account user to our Teams instance but was then met with an error message that only an Admin could approve the Retool, Inc. account app request. I passed this along to my admin and they were unable to facilitate the acceptance. Everything seems like it is correct on the MSFT and Teams side of things.

Does anyone know what changed on the Retool side of the equation?

4

Hi folks! I'll look into it internally. Thanks for flagging

1 Like
5

Seems like the Retool teams connector secret expired.

6

Hi @gata,

Thanks for chiming in! I am still discussing this with some folks internally, and I will follow up here when I have an update

7

We should have a fix for this bug soon. Thanks, everyone, for your patience!

8

This should be fixed now :slightly_smiling_face:

9

Looks like it was resolved for a while, but we are having the problem again now.

10

Thanks for flagging! I see some of the token failed errors in our logs as well - though it seems to be working for most orgs :disappointed: I am checking in with the on call team again

11

@gata, we haven't been able to reproduce this issue. Could you share a screenshot? What is the subdomain for your Retool org?

12

Seems like the problem resolved itself, I can't reproduce it on my end either. Thank you for your quick help! I'll reach back if I have any further issue on this.

1 Like
13

Yes, please do! Thank you :slightly_smiling_face: