temporalio / temporalio/temporal
Support changing system workflow cron schedule
Nobody has claimed this yet.
- 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.
Support changing system workflow cron schedule. Currently the cron schedule is hardcoded and even if the value in code is updated, when deploying the change, the cron schedule for the workflow won't be updated if there's already a workflow running.
Describe the solution you'd like
If describe existing workflow if running & has different cron schedule, terminateAndStart a new one with updated schedule.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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.
Research direction
The issue names no files, tests, or entry points. Trace how system workflows persist and compare their cron schedules, then review the existing terminate-and-start workflow behavior; done means a running workflow is replaced when its configured schedule changes and remains unchanged when it does not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100