Preserve NextRetryDelay across unrelated activity option updates#10920
Open
fretz12 wants to merge 2 commits into
Open
Preserve NextRetryDelay across unrelated activity option updates#10920fretz12 wants to merge 2 commits into
fretz12 wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Fixed standalone activity update-options retry handling so unrelated option updates no longer recalculate an already-scheduled worker-provided NextRetryDelay.
Why?
CurrentRetryInterval stores both retry-policy backoff and worker-provided NextRetryDelay. The old update path recalculated this field for any scheduled/paused activity update, so an unrelated update could overwrite a worker override and delay the next retry incorrectly.
How did you test it?