Skip to content

Conversation

@cathteng
Copy link
Member

We started handling fallthroughType correctly in dual writing here #106633

But we need a migration to fix the previously migrated email actions

@cathteng cathteng requested review from a team as code owners January 23, 2026 18:54
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 23, 2026
@cathteng cathteng marked this pull request as draft January 23, 2026 18:59
@cathteng cathteng marked this pull request as ready for review January 23, 2026 19:09
@github-actions
Copy link
Contributor

This PR has a migration; here is the generated SQL for src/sentry/workflow_engine/migrations/0106_fix_email_action_fallthrough_type.py

for 0106_fix_email_action_fallthrough_type in workflow_engine

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL
@github-actions
Copy link
Contributor

This PR has a migration; here is the generated SQL for src/sentry/workflow_engine/migrations/0107_fix_email_action_fallthrough_type.py

for 0107_fix_email_action_fallthrough_type in workflow_engine

--
-- Raw Python operation
--
-- THIS OPERATION CANNOT BE WRITTEN AS SQL
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

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.

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

2 participants