Skip to content

ref(seer): Restore Seer automation in post-process and widen the killswitch - #121486

Open
skonves wants to merge 2 commits into
masterfrom
ref/restore-seer-automation-post-process
Open

ref(seer): Restore Seer automation in post-process and widen the killswitch#121486
skonves wants to merge 2 commits into
masterfrom
ref/restore-seer-automation-post-process

Conversation

@skonves

@skonves skonves commented Aug 6, 2026

Copy link
Copy Markdown
Member

Summary

This PR does two things. It reverts #121426. It then makes the issue summary killswitch apply to every plan tier.

Revert of #121426

#121426 removed kick_off_seer_automation from GROUP_CATEGORY_POST_PROCESS_PIPELINE and from GENERIC_POST_PROCESS_PIPELINE. It also marked five tests in tests/sentry/tasks/test_post_process.py as xfail.

The first commit reverts that change. kick_off_seer_automation runs in both pipelines again. The five tests run and pass again.

Killswitch move

The seer.post-process-issue-summary-killswitch.enabled check sat inside the is_seer_seat_based_tier_enabled block. Only seat-based organizations obeyed the killswitch. The default tier reached generate_summary_and_run_automation even when an operator turned the killswitch on.

The second commit moves the check to the first statement of kick_off_seer_automation. The killswitch now stops all Seer work in post-process for both tiers.

Behavior change to note

This widens the reach of the option. generate_summary_and_run_automation on the default tier now respects the killswitch. Reviewers should confirm that this matches the intent of the option.

Tests

pytest tests/sentry/tasks/test_post_process.py -k seer passes. 25 tests pass.

skonves added 2 commits August 6, 2026 14:18
…)"

This reverts commit 5bca0c8.

Put kick_off_seer_automation back in GROUP_CATEGORY_POST_PROCESS_PIPELINE
and in GENERIC_POST_PROCESS_PIPELINE. Remove the five xfail marks that
the original commit added to the post-process tests.
The seer.post-process-issue-summary-killswitch.enabled check was inside
the is_seer_seat_based_tier_enabled block. Only seat-based organizations
obeyed the killswitch. The default tier still started Seer automation.

The check is now the first statement in kick_off_seer_automation. The
killswitch stops all Seer work in post-process for both tiers.
@skonves
skonves requested a review from a team as a code owner August 6, 2026 21:21

@cvxluo cvxluo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's coordinate with #121481 @trevor-e . i think we want to both:

  1. remove the seer.post-process-issue-summary-killswitch.enabled check
  2. add a new seer.post-process-issue-summary.rollout-rate so we can gradually roll this out

@trevor-e

trevor-e commented Aug 7, 2026

Copy link
Copy Markdown
Member

Sorry missed the ping for this. Yea seems like we can probably remove this now that seer.post-process-issue-summary.rollout-rate is deployed?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants