Repository navigation
feat(slack): Check Seer credits before running an agent chat mention - #130352
alexsohn1126 merged 2 commits into
Conversation
github-actions
Bot
added
the
Scope: Backend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit ff2979f. Configure here.
| thread_ts=thread_ts or ts, | ||
| status="", | ||
| ) | ||
| return |
There was a problem hiding this comment.
Out-of-credits halt sends no Slack message
Medium Severity
When the org is out of Seer credits, the mention handler records a halt and clears the thinking status, then returns without telling the user. Sibling halt paths (identity_not_linked, user_not_org_member) send an ephemeral Slack message, and the web chat equivalent returns a 402 with an explanation. Users will see is thinking... vanish with no reply and no indication they are out of credits.
Reviewed by Cursor Bugbot for commit ff2979f. Configure here.
There was a problem hiding this comment.
this will be a follow-up
ff2979f to
ea395dc
Compare
0683e3c to
fb435c6
Compare
Sentry Snapshot Testing
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
can_run_seer_operation now takes the Seer feature to bill against. Slack mentions run the agent chat, so they pass the explorer feature like the web chat endpoint does. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
fb435c6 to
0d60c3d
Compare
Adds Seer credit checks before processing
@Sentrymentions for Seer Agent calls in Slack.This one should be pretty straightforward. Once we have the organization of the Seer Agent call, we check whether we have quota before proceeding to trigger the agent.
However, it is important to know how we got the organization in the first place.
When we receive a Slack webhook from a user mentioning Sentry, we have to resolve which organization the webhook is from. The issue is, if there are multiple Sentry organizations linked to a single Slack Workspace, we are not able to tell which organization it is from 😵
We use heuristics to guess the organization we should be looking at, but this is not bulletproof by any means.
All that is just to say -- if there are multiple Sentry orgs linked to a single Slack workspace, the quota check may go to the wrong place, and we won't know when it happens (other than users telling us) 🫤
Fixes CW-2342