Grok Bot Sentry issueCreated Routine never triggers despite new Sentry Issue

Support Bug Reports
,
1

Describe the Bug

Hi,

I’m having an issue with a Grok Bot Routine using the Sentry “issueCreated” trigger.

The Routine is enabled, but it has never run and lastRunAt remains empty.

Setup:

  • Grok Bot: PULSE Engineering Lead
  • Routine trigger: Sentry → issueCreated
  • Routine status: Enabled
  • Project scope: All Sentry projects
  • Sentry account is connected through Cursor Dashboard → Integrations
  • This is NOT using the Sentry plugin/MCP

What I tested:

  1. Created the Routine with issueCreated.
  2. Connected the correct Sentry organization to Cursor.
  3. Verified the Routine remained enabled after connecting Sentry.
  4. Sent a completely new Sentry event AFTER the Sentry connection was established.
  5. The event used:
    • environment: production
    • level: error
    • a unique message/timestamp
    • a unique Sentry fingerprint to guarantee a new Issue
  6. Sentry accepted the event successfully (HTTP 200).
  7. A brand-new Issue appeared in Sentry.
  8. The Grok Bot Routine did not trigger.
  9. Routine history still says no runs / lastRunAt is empty.

Test event:
Event ID:
b75236c26cfb4c9793f37d1e714563e2

Issue title:
PULSE-ROUTINE-PROBE 2026-09-02T12:58:04.603Z — one-off check of the Sentry issueCreated webhook. Not a real error. No user data.

The event intentionally contained no user data or sensitive information.

Expected behavior:
New Sentry Issue
→ issueCreated trigger fires
→ Grok Bot Routine runs
→ PULSE Engineering Lead receives the event.

Actual behavior:
New Sentry Issue is successfully created, but the Routine never runs.

Important:
This does not appear to be caused by filtering inside the Routine prompt because the Routine itself never starts.

Could you check whether the Sentry issueCreated event subscription/webhook is actually registered and active for this Routine/account?

Please also let me know if there is any additional connection step required for Sentry event triggers beyond:
Cursor Dashboard → Integrations → Sentry → Connected.

Thanks.

Steps to Reproduce

  1. Create a Grok Bot Routine with the Sentry “issueCreated” trigger.
  2. Enable the Routine.
  3. Connect the Sentry organization through Cursor Dashboard → Integrations → Sentry.
  4. Send a new Sentry event after the connection is established.
  5. Use environment=production and level=error.
  6. Ensure it creates a completely new Sentry Issue (we also used a unique fingerprint to guarantee this).
  7. Verify that the new Issue appears successfully in Sentry.
  8. Check the Grok Bot Routine.

Result:
The Sentry Issue is created successfully, but the Routine never triggers. The Routine still shows no runs and lastRunAt remains empty.

Operating System

Windows 10/11

Version Information

גרסה: 0.30.0
ערוץ הפצה: stable
מערכת הפעלה: win32

Does this stop you from using Cursor

Yes - Cursor is unusable

8

Hey @directs1357-lang, thanks for the report, and thanks for your patience!

Good news first: the routine you recreated last night did fire. Sentry sent us a new issue event late last night, it matched your Sentry routine, and your bot picked it up and ran it for under a minute. You should see that run in the routine’s history now.

About the earlier probe you ran during the day: your Sentry connection and the routine were both in place at that time, but Sentry never sent us an event for it, so there was nothing for the routine to react to. The most common reasons are the event landing in a project that belongs to a different Sentry organization than the one you connected, or the event not creating a brand new issue on Sentry’s side.

Two quick things so I can confirm you are fully unblocked:

  1. Open the routine in Grok Bot and check its run history. Do you see a run from late last night?
  2. Did your bot post anything in the chat for that run? If your routine prompt is meant to stay quiet unless something matches, that is expected. If it should have said something and did not, let me know.