I’m having a recurring issue with the Microsoft Teams Trigger node and wanted to check if anyone else has experienced this.
The trigger works fine in test mode (“Execute and wait”), but in production it stops receiving events automatically, even with the workflow active and published. Credentials are valid and Azure permissions are correctly granted.
The only fix I found is deactivating and reactivating the workflow, which forces the polling to restart — but the problem keeps coming back.
Has anyone found a permanent solution for this? Is there a configuration I’m missing?
1 Like
Welcome @Aurora_JAZ!
The Microsoft Teams Trigger in n8n uses polling (it checks for new activity every few seconds), but the underlying Microsoft Graph API subscription used to stream events can expire. When the subscription lapses, the trigger silently stops receiving events even though the workflow is active.
The permanent fix: Microsoft Graph subscriptions have a maximum expiry window (typically 1-3 days depending on the resource). You need a separate scheduled workflow that runs daily and calls PATCH https://graph.microsoft.com/v1.0/subscriptions/{subscriptionId} to renew the expiration date. The subscriptionId is logged when the trigger first activates - you can find it in the execution log of the first successful trigger run. This stops the recurring drop-off without needing to deactivate and reactivate manually.