Skip to content

feat(seer): Send stopped and errored webhooks to Sentry Apps - #131746

Open
NicoHinderling wants to merge 3 commits into
masterfrom
nico/feat/autofix-stopped-errored-webhooks
Open

NicoHinderling wants to merge 3 commits into
masterfrom
nico/feat/autofix-stopped-errored-webhooks

Conversation

@NicoHinderling

Copy link
Copy Markdown
Contributor

Sentry Apps couldn't tell when a Seer run stopped early or failed, while Slack and issue activity could. This makes seer.stopped and seer.errored available to Sentry Apps. Refs AIML-3861.

  • Apps opt in by ticking the new events. Apps saved before this keep their stored event list and don't get them.
  • seer.stopped (single runs) sends run_id, sentry_run_id, group_id and stop (reason, suggestion).
  • seer.errored (all runs) sends run_id, sentry_run_id, group_id and failure_reason (timeout, stalled, out_of_credits, pr_creation_failed).
  • Both are sent from the same places that notify Slack today, even when the org has no Slack set up.

Add seer.stopped and seer.errored to the Seer webhook events so Sentry Apps can opt in to them. Apps saved before this keep their stored event list and only receive the new events once they select them.
Broadcast seer.stopped and seer.errored to subscribed Sentry Apps from the same places that notify Slack, and add sentry_run_id to both payloads to match the other Seer events. Apps get them even when the org has no entrypoints.
@NicoHinderling
NicoHinderling requested review from a team as code owners November 19, 2026 01:28
@linear-code

linear-code Bot commented Nov 19, 2026

Copy link
Copy Markdown

AIML-3861

@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Nov 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant