chore(seer-activity): Remove unused flag#119081
Conversation
| manager.add("organizations:workflow-engine-metric-detector-limit", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=True) | ||
| # Enable seer activities to be evaluated in workflow engine | ||
| manager.add("organizations:workflow-engine-evaluate-seer-activities", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=False) | ||
| # Enable our logs product (known internally as ourlogs) in UI and backend |
There was a problem hiding this comment.
Bug: The feature flag organizations:workflow-engine-evaluate-seer-activities is being de-registered while still being used in multiple production code paths, which will cause silent functional regressions.
Severity: HIGH
Suggested Fix
Ensure that the dependent pull request which removes all usages of the organizations:workflow-engine-evaluate-seer-activities feature flag is merged before this pull request. This will prevent a state where the flag is de-registered but still referenced in active code.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: src/sentry/features/temporary.py#L402
Potential issue: This pull request removes the registration for the feature flag
`organizations:workflow-engine-evaluate-seer-activities`. However, this flag is still
actively used in four production code paths. The `features.has()` check for an
unregistered flag will silently return `False` instead of raising an error. This will
cause silent functional regressions by disabling Seer activity processing across all
dependent code paths, such as skipping seer activity handlers, falling back to different
notification logic, and filtering out `SEER_ACTIVITY_TRIGGER` conditions from API
results.
Also affects:
src/sentry/workflow_engine/handlers/workflow/workflow_activity_handlers.py:63src/sentry/notifications/notification_action/utils.py:59src/sentry/notifications/notification_action/action_handler_registry/webhook_handler.py:66src/sentry/workflow_engine/endpoints/organization_data_condition_index.py:71
Did we get this right? 👍 / 👎 to inform future reviews.
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 d2f7264. Configure here.
| manager.add("organizations:workflow-engine-issue-alert-endpoints-put", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=False) | ||
| # Enable metric detector limits by plan type | ||
| manager.add("organizations:workflow-engine-metric-detector-limit", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=True) | ||
| # Enable seer activities to be evaluated in workflow engine |
There was a problem hiding this comment.
Flag removal disables seer paths
Medium Severity
Removing registration for organizations:workflow-engine-evaluate-seer-activities while production code still gates seer-activity workflow handling, notifications, and the data-condition index on features.has for that name makes those checks always evaluate false once the flag is unregistered. Tests that enable the flag via Feature or with_feature also fail because the test helper requires a registered feature.
Reviewed by Cursor Bugbot for commit d2f7264. Configure here.
Backend Test FailuresFailures on
|


Requires #119068 and https://github.com/getsentry/sentry-options-automator/pull/8533 in order to merge