Parsing natural-language cron schedule phrases
Cluster 51975 · cron. Data as of
Nothing open on GitHub. Fix merged in #98271 on 30 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #98271. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #98271. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address problems with parsing natural-language schedule expressions (such as weekday-at-time phrases) into valid cron expressions. A gap exists where the desktop interface advertises schedule formats that the parser does not accept.
Open issues0
Open PRs0
Fixes on record
-
#98271 fix(cron): Desktop's advertised natural schedules now parse (#51975, salvage #51598 #52504)
files:
cron/jobs.py,tests/cron/test_jobs.py,tests/tools/test_cronjob_tools.py,tools/cronjob_tools.py,website/docs/user-guide/features/cron.md
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
Closed issues · 1
- Closed#51975fix(cron): Desktop advertises natural schedules that parse_schedule rejects
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- cron
- Merged PRs
- #98271
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 30 Aug 2026