METAGROK
GROK BOT / fix-grok-bot-sentry-issuecreated-routine

Fix a Grok Bot Sentry issueCreated routine that never runs

fix-grok-bot-sentry-issuecreated-routine

Use this when a Sentry issueCreated routine you set up never runs. The routine can stay enabled with no recent run 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 and inspect its recent run history for a new run or a failure (docs.x.ai/grok-bot/skills-routines-and-automations, checked 2026-09-25).

If run history shows no new run after a verified new Issue in the scoped project, the miss is on the Sentry integration path, not a time-based 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.

Related

Pitfalls

  • Reusing an old Issue will not prove issueCreated delivery. Create a new one after Connected.
  • An enabled toggle with no new run in run history 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.