Hi @julianhernandez,
Welcome to Microsoft Q&A, and thank you very much for reaching out.
Based on your description, may I confirm whether this issue started recently or has been happening for some time?
From my research, Teams change‑notification subscriptions have a maximum lifetime of 60 minutes, and they must be proactively renewed before they expire.
According to Microsoft documentation, if a subscription is created with an expiration time longer than one hour without a
lifecycleNotificationUrl, the request fails, and Microsoft Graph will stop delivering notifications once the subscription expires.
Microsoft also requires your application to renew the subscription or respond to lifecycle notifications before expiration. Otherwise, Graph will no longer send change notifications.
To help prevent this issue, ensure your application renews subscriptions well before expiration, such as schedule a renewal when roughly half of the lifetime has elapsed, which avoids relying solely on lifecycle events.
Also, you can review these Microsoft Graph documentation on subscription lifecycle events here for additional details: Microsoft Graph Subscriptions Documentation & Reduce missing subscriptions and change notifications.
Regarding the token aspect, a failed or expired access token would normally prevent the subscription from being renewed at all. Since you were able to renew the subscription successfully based on your description, it is unlikely that the token itself is the root cause of the issue.
I hope this helps.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.