For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Hey @William_Crawford, thanks for the report, the screenshots, and all the troubleshooting steps.
Your automation setup looks right. Plain messages (without an @mention) in the watched channel are supposed to trigger “New message in Teams channel” automations. For that to work, Microsoft Teams has to deliver those messages to the Cursor app, and Teams only does that when the app has been granted permission to read that team’s channel messages. From what we can see, plain posts from your Teams organization aren’t reaching Cursor at all, so the trigger never gets a chance to match. Channel Created events and Run Test use a different path, which is why those work.
Reconnecting from cursor.com usually won’t fix this on its own, because the permission is granted inside Teams. Could you try this:
Ask your Microsoft 365 / Teams admin to confirm that resource-specific consent for Teams apps is allowed in your organization (the Teams admin center setting that lets team owners give apps access to their team’s data).
As an owner of the team that contains the Alerts (dev) channel, open the team in Teams, go to Manage team > Apps, and remove the Cursor app.
Add the Cursor app back to that team and accept the permissions prompt (it should list reading the team’s channel messages).
In the watched channel, start a brand-new post (not a reply in an existing thread) without mentioning @Cursor.
I am also experiencing the same issue. Tried similar t/s steps and Cursor never responds to new chats in teams. Grok Bot also experiences the same issue. It can not detect/respond to new messages in Teams in real time. It does work if I set it to check every 5 minutes instead of real time in Grok Bot.. but the timer test did NOT work in Cursor automation.
I’ve followed your steps, but maybe we’re still wrong from the Teams admin side.
As a team owner, when I go to re-add the app to a team,
I’m starting with + → Apps → Manage your apps → Get more apps → Search cursor → Add.
And then I reach this point and after clicking go, I’m not seeing a permission request.
Hey @William_Crawford, thanks for running all of that and for the admin output and screenshots.
Your Teams setup looks right. The consent setting your admin shared is the default, the permissions are listed, and new Teams doesn’t show a separate permission prompt when you add an app, so you didn’t miss a step.
Your test messages did reach us, and we found the cause on our side: your team uses an older Microsoft ID format for its channels, and our trigger matching doesn’t recognize that format yet. Messages from those channels are skipped before the trigger is checked, which is why nothing runs. That includes @Cursor mentions, so the @mention workaround I suggested earlier won’t help in your case, sorry about that.
I’ve passed this to the team. There’s nothing more you need to change in Teams or your admin settings in the meantime.
@mosdef, your organization doesn’t appear to be affected by this specific issue, so we want to look at yours separately. It might be worth starting a new thread.
Hey @William_Crawford,
Quick update: the fix for channels that use the older ID format has been made on our side and will be rolled out soon if it hasn’t been already. You don’t need to change anything in Teams or in your automation.
Once it’s live, a new top-level post in the watched channel should start a run, and @Cursor mentions there will trigger it too.
Could you give it another try and let me know if nothing shows up in Run History? If it still doesn’t fire, the approximate time (and time zone) of your test post would help us dig in.