Skip to content

[Scheduler] Always attempt DeleteSchedule on both stacks#10197

Open
lina-temporal wants to merge 1 commit intomainfrom
delete-schedule-both-stacks
Open

[Scheduler] Always attempt DeleteSchedule on both stacks#10197
lina-temporal wants to merge 1 commit intomainfrom
delete-schedule-both-stacks

Conversation

@lina-temporal
Copy link
Copy Markdown
Contributor

@lina-temporal lina-temporal commented May 7, 2026

What changed?

  • Delete is now called for both CHASM/V1 stacks, as long as CHASM is enabled, regardless of success/error from CHASM stack.

Why?

  • CHASM block successfully deleting means that the V1 handler never gets a chance to run, blocking V1 deletes after a schedule has gone from V1->V2->V1 (rollback).

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

@lina-temporal lina-temporal requested a review from chaptersix May 7, 2026 21:57
@lina-temporal lina-temporal requested review from a team as code owners May 7, 2026 21:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@chaptersix chaptersix Awaiting requested review from chaptersix

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@lina-temporal