Defer schedule catchup window default to server#1646
Closed
chaptersix wants to merge 1 commit into
Closed
Conversation
|
|
1 similar comment
|
|
tconley1428
reviewed
Jul 15, 2026
|
|
||
| ### Fixed | ||
|
|
||
| - Schedule policies now omit an unspecified catch-up window so the Temporal Server applies its |
Contributor
There was a problem hiding this comment.
Seems like this needs a breaking change notification.
Author
There was a problem hiding this comment.
hmm, on seconds thought. I think it's fine to for an SDK to default to a year.
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
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
SchedulePolicy.catchup_windowfrom an SDK-defined year toNone.Nonewhen decoding.Why
The server owns the default. Materializing one year in the SDK prevents server-side default changes from applying consistently.
Breaking changes
An unconfigured policy now exposes
Nonebefore it is sent to the server. Described schedules continue to expose the server-resolved duration.