temporalio / temporalio/temporal
Support configuring maxCalendarYear for Schedules beyond 2100
Open
@chaptersix is already working on this.
Since Apr 20, 2026.
enhancement
schedules
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
The maxCalendarYear for Schedules is currently hardcoded to 2100.
- This prevents users from scheduling workflows or timers that need to extend beyond that year, which can be a blocker for long-running or far-future scheduling use cases.
- or are expected to update Schedules once this limit is increased
Describe the solution you'd like
Either increase the default maxCalendarYear limit, or make it configurable via DynamicConfig so that operators can adjust it without requiring a code change or redeployment.
Describe alternatives you've considered
Additional context
- this was a question from customer for payments
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.