Skip to content

Do not bypass task generation when version changes #7890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 10, 2025
Merged

Do not bypass task generation when version changes #7890

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6ea69d0
Do not bypass task generation when version changes
ShahabT Jun 10, 2025
9acab45
compare using transition
ShahabT Jun 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions service/history/api/respondworkflowtaskcompleted/api.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -536,6 +536,12 @@ func (handler *WorkflowTaskCompletedHandler) Invoke(
}
}

if ms.GetDeploymentTransition() != nil {
// Do not return new wft to worker if the workflow is transitioning to a different deployment version.
// Let the task go through matching and get dispatched to the right worker
bypassTaskGeneration = false
}

var newWTErr error
// If we checked WT heartbeat timeout before and WT wasn't timed out,
// then OriginalScheduledTime needs to be carried over to the new WT.
Expand Down
Loading