Grok Bot Sentry Routine auto-trigger failure

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

The Grok Bot Routine Sentry listener does not react to real Sentry issue creation or update events. Direct Sentry ingest returns HTTP 200, Sentry creates the issue, and the existing Sentry-to-Telegram notification succeeds within about one minute. However, the Routine remains at lastRunAt: null with “No runs yet”. Manual Test run / Run now succeeds, but it contains no Sentry issue payload and is labeled “user pressed Run now”. Both Routines were Active during testing and were deactivated afterward.

Steps to Reproduce

  1. Create a Sentry Routine in Grok Bot and select only Sentry project 4511442570313728 (haccp-selo).
  2. Set trigger to issueCreated and keep the Routine Active.
  3. Send a unique test event directly to Sentry ingest with environment=production and tag test=true.
  4. Verify ingest returns HTTP 200 and Sentry creates a new issue.
  5. Wait and check the Routine Run history without manually asking the bot to investigate.
  6. Repeat with a second temporary Active Routine using issueAny.
  7. Press Test run / Run now manually on the Routine screen for comparison.

Test A: SELO_ROUTINE_ISOLATED_TEST_2026-08-15_00-27-36 (issueCreated)
Test B: SELO_ROUTINE_V2_TEST_2026-08-15_00-35-15 (issueAny)

Expected Behavior

Each new Sentry issue event for the selected project should wake the Grok Bot Routine automatically and create a Sentry-triggered entry in Run history with the issue payload. Manual Run now should not be required.

Screenshots / Screen Recordings

codex-clipboard-yJlgsA.png
codex-clipboard-yJlgsA.png610×1220 55.1 KB

Operating System

MacOS

Version Information

Grok Bot web app, tested 2026-08-15 KST in Chrome on macOS. Cursor IDE/CLI version is not applicable to this web Routine listener issue.

For AI issues: which model did you use?

Not applicable - this is a Grok Bot Routine event-listener issue, not a model-output issue.

For AI issues: add Request ID with privacy disabled

No Request ID is available because the automatic Routine never started. The only successful run was a manual Run now and had no Sentry issue payload.

Additional Information

Bot name: 셀로실장
Sentry connector: connected; whoami succeeded
Project: haccp-selo (4511442570313728)
Routine A: 업체 오류 운영 점검; internal ID automation-1786718710008; issueCreated; lastRunAt null; 0 automatic runs
Routine B: 업체 오류 운영 점검 v2; issueAny; 0 automatic runs
Manual Run now succeeded at 2026-08-15 00:38:29 KST, but had no Sentry payload
The existing Sentry-to-Telegram path delivered both test alerts in about one minute.
Both Routines were Active during testing and were deactivated afterwards.
Sensitive data omitted: email, private Sentry URLs, event IDs, DSN, tokens, webhook secrets, and SSH keys.

Please check whether the Grok Bot Sentry listener subscribes to issueCreated / issueAny for the connected Sentry account, and whether issues created through Sentry ingest are dropped before reaching the Routine listener.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hi @insoo970923!

Thanks for flagging this.

Could you check whether Sentry is connected at https://cursor.com/dashboard/integrations? It’s not ideal that there’s no easy path to do this within Grok Bot, but connecting it in the dashboard should establish the necessary link.