Critical data loss and event desynchronization in Teams custom app after tenant-level changes

Hi Hamed Amadli, Kasmir,

Thank you for posting your question in the Microsoft Q&A forum.

Based on what you’ve observed, your custom bot appears to be experiencing the detailed observations across multiple components, with symptoms surfacing after the detailed observations. Because these behaviors often involve deep tenant configuration and backend service interactions (which Microsoft Support can directly inspect), I highly recommend opening a Support ticket via your Azure Portal. That route will enable live agents to review tenant policies, app channel configuration, and service logs end‑to‑end.

In parallel, I’ve researched and consolidated a few actionable insights that may help you mitigate the current situation:

1) Symptom: Bot conversation references become invalid, causing proactive messages to silently fail without errors

Microsoft has mentioned a scenario affect proactive messaging here: https://learn.microsoft.com/en-us/azure/bot-service/channel-connect-teams?view=azure-bot-service-4.0#test-your-bot-in-teams

While that scenario can be rare, a more common pattern is that conversation objects can gradually become stale, breaking proactive messaging unless you refresh references. A helpful community discussion with mitigation ideas is here: https://techcommunity.microsoft.com/discussions/teamsdeveloper/teams-bot---user-conversation-objects-are-becoming-stale-breaking-the-ability-to/3887850

2) Symptom: Tab state and configuration reset for some users

I did not find a confirmed public report matching this behavior precisely. Because tenant‑level policy/app‑catalog refreshes can re‑initialize clients and cause cache inconsistencies, an immediate troubleshooting step is to clear the Teams cache and restart the Teams client for affected users, then confirm whether the issue persists.

3) Symptom: Graph webhook subscriptions appear active, but change notifications stop intermittently

Microsoft notes for Teams resources: https://learn.microsoft.com/en-us/graph/teams-change-notification-in-microsoft-teams-overview

While this doesn’t directly explain intermittent stops, a plausible cause is renewal gaps: if the authorization used to renew (e.g., access token) expires, intermittently returns 403, or renew calls are delayed under service latency, notifications can pause even though the subscription shows “Active.”

4) Symptom: Adaptive Card actions trigger invokes events inconsistently

Recent user reports indicate potential regressions or breaking changes that can affect invoke handling. See: https://learn.microsoft.com/en-gb/answers/questions/5662424/is-there-a-known-breaking-change-in-recent-teams-u

For further troubleshooting, because you’ve already correlated incidents with tenant‑level operations, consider a canary rollout approach: Apply policy or catalog changes to a subset of users, observe whether these users exhibit higher failure rates, and only then roll forward.

I hope the above insights help you mitigate the current behavior while your Support ticket progresses.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

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.