Teams/Asana connection sent task updates, when the settings had only status updates selected.

I have my Asana project connected to a Teams Chat. When I set it up, I made sure the settings had only Project Statuses being posted to the chat. It has worked, mostly as expected, since I set it up a month ago.
This afternoon, I created a new task in the project. It immediately posted the activity to Teams. That should not have happened. This is a chat with our executive stakeholders who do not need to be spammed with that activity. I went into the settings to check… I had to log in again, but then confirmed that my notifications settings were correct.

Why did this happen?

Hi @anon73702394! It looks like there may be more than one Asana subscription connected to that Teams chat. If a second subscription is still set to post task activity, duplicates can happen, especially if someone reconnected the project and the connection defaulted some settings back on. Another possibility is that a project rule in Asana is posting to Teams separately from the channel subscription.

To fix this, open the Teams chat, go to Apps > Asana > Manage (or Channel settings > Connectors), and review all subscriptions. Remove any duplicates or anything set to tasks/activity, keeping only the one limited to Project Status. Then edit the remaining subscription, toggle off all task‑related options, and save. If it already looks correct, disconnect and reconnect the project, making sure to choose only Project Status during setup. In Asana itself, check Project > Customize > Rules to see if any rule has a “Post to Microsoft Teams” action — if so, pause or narrow that rule.

Finally, test in a non‑executive chat by creating a throwaway task to confirm no posts, then reconnect the executive chat. Also, check if anyone else recently connected the same project to that chat.

This way, you’ll ensure only project status updates are sent to your stakeholders, without extra task activity slipping through.