Fix a Grok Bot Sentry issueCreated routine that never runs

A Sentry issueCreated routine can stay enabled with an empty lastRunAt even after a brand-new Issue appears in Sentry. Cursor account integrations start event routines; they sit apart from the Sentry plugin or MCP. For schedule and auth misses, see Fix a Grok Bot routine that did not run.

Confirm the integration path

1. Open the owning Bot → View conversation details → Routines and open the Sentry routine.
2. Confirm the trigger is Sentry → issueCreated, the routine is enabled, and the project scope matches the Issue (or All projects).
3. In Cursor Dashboard → Integrations → Sentry, confirm the organization shows Connected.
4. Create a new Sentry Issue after Connected (a unique fingerprint helps). Confirm the Issue appears in Sentry.
5. Wait for delivery, then refresh the routine detail. Check lastRunAt and any failure note.

If lastRunAt stays empty after a verified new Issue in the scoped project, the miss is on the Sentry integration path, not a cron schedule.

Miss checklist

• Wrong surface: Plugins → Sentry or an MCP Sentry tool does not arm Cursor Integration routines. Use Dashboard → Integrations → Sentry.
• Project filter: A narrowed project list ignores Issues from other projects.
• Reconnect: Disconnect and reconnect Sentry in Integrations if Connected looks stale, then create another new Issue.
• Other events: issueResolved / issueAssigned / issueArchived / issueUnresolved / issueAny need their own event case; issueCreated only fires on create.

Official skills/routines docs: event listeners fire through Cursor account connections. Troubleshooting also covers reconnecting an integration when a listener stays quiet.

Pitfalls

• Reusing an old Issue will not prove issueCreated delivery. Create a new one after Connected.
• An enabled toggle with empty lastRunAt is still a miss until a matching Issue lands after the connection is healthy.
• Do not assume a plugin install replaces Integrations → Sentry for this trigger.