Microsoft Teams trigger disconnects?

Questions
1

Hi, I’ve created a two part automation, where the first part sends me a list of items on Microsoft Teams as a chat message, this usually works fine.
The second part of the automation is triggered from a message I send to that same Microsoft Teams chat which works, but for some reason it unplugs/disconnects itself from Microsoft Teams every now and then, resulting that I get the message from Automation A, but when I try to do something about that Automation A the Automation B does not trigger because Microsoft Teams is “no longer listening”. Any tips on how to keep it “listening”?

Describe the problem/error/question

No error message

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

This is a known problem of the Teams trigger node because the subscription is only valid for a certain time (I think 72h but not sure). As a workaround, I made a small flow that runs every night and unpublishes the corresponding flow, waits a few seconds and publishes it again. Republishing will also renew the subscription.

1 Like
3

Thanks @AccelyBiz, I created the same type of flow to deactivate/activate the workflows.
Hope this resolves the issue for good.

1 Like