Repository navigation
feat(investigations): Validate action request events - #128421
Merged
Merged
Conversation
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. Accept Seer's action request and withdrawal events, so Sentry can store what Seer suggests. Each action kind owns its payload contract, so new kinds don't change the shared one.
github-actions
Bot
added
the
Scope: Backend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
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.
Reviewed by Cursor Bugbot for commit dc0b350. Configure here.
billyvg
reviewed
Oct 21, 2026
Reject IDs and windows past their column limits, keep trim from fixing a malformed action, and log each dropped request once, on the apply path.
Store typed actions from the first ingest PR on, and type validated requests so callers don't cast.
Say what trim drops and why, now that the limits are policy.
billyvg
approved these changes
Oct 21, 2026
Make the comments read plainly.
wedamija
added a commit
that referenced
this pull request
Oct 21, 2026
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click. Save the requests Seer sends during and after a run, and keep them current as Seer revises, withdraws, or replaces them, so Sentry always shows Seer's latest suggestions. Depends on #128421.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of a series that adds follow-up actions to Seer investigations: when a run completes, Seer suggests one next step, and the user can apply a typed action, such as a monitor change, with one click.
Accept Seer's action request and withdrawal events, so Sentry can store what Seer suggests. Each action kind owns its payload contract, so new kinds don't change the shared one.