Grok Bot: GitHub "issue assigned" routine never fires (5 attempts, recreated routine, app has repo access)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

A Bot-owned routine with a GitHub “issue assigned” trigger never starts, even though the assignment event exists on GitHub, the Cursor GitHub App has access to the repository, and the Bot handles the same issue fine when asked in chat.

Setup

  • A Bot owns one routine, shown in the routine panel as: When an issue is assigned in <my-account>/<private-repo> (by @<second-account>), no schedule, status Active.
  • <second-account> is a separate GitHub user added as a collaborator on that private repo. A server-side job uses its token to create an issue via the REST API with assignees: ["<my-account>"], plus labels.
  • The issue timeline confirms the event: assigned, actor <second-account>, assignee <my-account>.
  • GitHub integration is connected in the Cursor dashboard as my personal account; the Cursor GitHub App is installed on that account with All repositories and read/write on issues.

Related: webhook routines are not a workaround here, because of the known issue tracked in Desktop Grok Bot webhook routine shows no POST URL / crsr_ key (Windows 0.47.0)

Steps to Reproduce

  1. Create the routine above from chat.
  2. Create an issue in the repo as <second-account>, assigned to <my-account>.
  3. Wait several minutes.

What I tried (all times UTC, 2026-09-15)

Issue created and assigned Condition Result
19:21:44 before the Cursor GitHub App was installed no run
19:37:55 before the Cursor GitHub App was installed no run
19:42:46 after installing the app with All repositories no run
19:47:15 after deleting and recreating the routine no run
20:17:03 after enabling on-site GitHub notifications; the “You were assigned” notification arrived in my inbox at 20:17:24 no run

Ruled out: repository access, since the Cursor app has All repositories and read/write on issues; routine age, since a recreated routine behaves the same; on-site notifications, since after I enabled them the assignment notification reached my GitHub inbox within about 20 seconds and the routine still did not run.

Expected Behavior

Expected: the routine runs and the Bot handles the issue.

Actual: no run in the routine history and no activity in the Bot’s chat. Asking the Bot in chat to handle the same issue works fine, so the Bot, its GitHub tools and the repo access are OK. Only the event trigger is silent.

Operating System

MacOS

Version Information

Grok Bot:
Version: 0.51.0
OS: darwin (macOS 26.6.2, Apple Silicon)
Plan: SuperGrok, Privacy Mode on

Additional Information

Questions

  1. Should an issue assigned routine fire when a different collaborator account creates the issue with the assignee already set, rather than assigning it afterwards?
  2. Does the trigger listen for a specific webhook event, for example issues.assigned rather than issues.opened carrying assignees, and does the “(by @user)” filter compare the assigner, the issue author, or the assignee?
  3. Is there a way to see received or unmatched events for a routine, to tell “not delivered” from “delivered but filtered”?

Thanks. I can share exact timestamps or routine IDs privately with the team.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. Extra thanks for the timings table and for checking access, the routine itself, and notifications upfront.

Main point first: your setup is correct. This isn’t a configuration issue on your side. It’s a known issue on our side that we’re already tracking. The GitHub issue assigned trigger currently doesn’t fire for github.com repositories, so the routine won’t start no matter how the assignee is set. Your access, routine, and filter are fine.

On your questions:

  1. Yes, by design the routine should also trigger when a collaborator creates an issue with an assignee set right away. In that case GitHub sends a separate assigned event.
  2. The trigger listens specifically to the assignment event assigned. The filter (by @user) checks who assigned it (the assigner), not the author or the assignee. In your case the collaborator is both the creator and the assigner, so the setup matches.
  3. There’s currently no user-facing log of received or non-matching routine events. Agree it would be useful, I’ve passed this on as feedback.

Temporary workaround: since webhook-routine doesn’t work for you due to 171324, the most reliable option right now is a scheduled routine. For example, every 15 minutes on weekdays, have the Bot check the repo for open issues assigned to you that it hasn’t processed yet, then handle them. If you prefer, a Slack trigger also works.

I can’t share an ETA for the event trigger fix yet, but I’ll post an update here when I have one.