Microsoft Teams connector only triggers for one user

We’re in the process of connecting our GrokBot to our MS Teams environment. We’ve created a Teams “Team” for the users who should have access, and added the Cursor app/integration, as well as registered the Teams connector inside of the GrokBot UI.

The bot is able to quickly respond to messages that I direct at it, but any other user doesn’t trigger a response until the bot actively polls (which can only happen as fast as every 5 minutes).

I’m trying to understand if this is a misconfiguration issue or a bug in the connector. We’re not actively using any other Cursor products or features at this time, so is it possible that the Cursor app that’s in the Teams Team may not be fully configured?

Hey @Advocate_Financial,

This isn’t a Teams permissions or consent problem: the Cursor app in your Team is receiving the channel’s messages fine. Your bot reads and posts through its own Teams account, and the instant reply comes from your General channel routine, which the Cursor app in the Team starts. The 5-minute routine is the backstop that catches anything the instant one misses.

The gap is in how messages reach that instant routine. When someone @mentions the Cursor app itself and their Teams account isn’t linked to a Cursor account, Cursor replies with a “connect your account” prompt and your routine doesn’t start, so that message waits for the 5-minute check. Your Teams account is the only one linked, which is why your messages get answered right away. As far as I can tell, linking your teammates’ accounts wouldn’t route their @Cursor mentions to your routine either, because those get matched against their own routines.

What works better today: ask teammates to address the bot by @mentioning its own Teams account or by name, without @mentioning Cursor. Posts like that are passed to your routine as they arrive. (An @Cursor mention also tries to start a separate Cursor coding agent, which is likely where any “couldn’t launch” reply you’ve seen comes from.)

Some posts that don’t mention Cursor also seem to miss the instant routine. I’ve passed that to the team to look into, and the 5-minute check keeps catching those in the meantime. If a teammate’s post without an @Cursor mention still waits for the poll, reply here with its time and channel and we’ll trace that one.

Hey Colin, thanks for the quick response!

You said @mentioning the Cursor app triggers the link your account prompt, but since we don’t actually use Cursor (other than this specific integration) we’re not really trying to interact with that app. I can have everyone call Cursor and link accounts if you think that’ll work, but it does feel odd when we just want the GrokBot.

@mentioning the GrokBot’s account works when I do it, but not when my teammate does, which is why I wondered if there was some requirement around the Cursor integration. When asked, the GrokBot talks about managing automations through the Cursor interface, but (presumably because all of this is being done through GrokBot) I don’t see anything configured in there.

Hi @Colin,

We’re still having issues with our GrokBot not responding quickly to Teams messages from users who haven’t linked a Cursor account. Is there anything we can do on our end to fix this and get instant replies, without having everyone set up in Cursor?

There doesn’t seem to be a good way to manage or monitor GrokBot created routines outside of GrokBot itself, and nothing shows up when I look at the Cursor settings/management pages (since I haven’t created anything in Cursor, just GrokBot).