Cron job repeat string values causing type errors
Cluster 7142 · cron. Data as of
3 open items. Fix merged in #98290 on 30 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 13 related items grouped here, 4 issues already closed.
- Fix event
- A fix was merged to main in PR #98290. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 3 PRs.
Most members concern the cron tool receiving string values like 'forever' or 'once' for repeat/times where an integer is expected, causing a str-vs-int TypeError, with several proposed coercion or normalization changes. One member is about how bare '30m' schedules versus 'in 30m' are interpreted, which appears to be a separate scheduling topic.
Open issues0
Open PRs3
Fixes on record
-
#98275 fix(cron): bare '30m' schedules recur as documented; 'in 30m' is the one-shot (salvage #78928)
files:
cron/jobs.py,tests/cron/test_claim_job_for_fire.py,tests/cron/test_jobs.py,tests/cron/test_oneshot_dispatch_failure_run_claim.py,tests/cron/test_terminal_job_rearm.py,tests/hermes_cli/test_web_server_cron_profiles.py,tests/test_timezone.py,tools/cronjob_tools.py,website/docs/user-guide/features/cron.md -
#98290 fix(cron): repeat='forever' no longer breaks job updates (completes the string-repeat class)
files:
cron/jobs.py,tests/cron/test_jobs.py,tools/cronjob_tools.py
4 PRs closed without merging
From the close comments: done elsewhere 2 · merged via another change 2
-
#7216 fix(cron): normalize string repeat values · done elsewhere →
89b38ed,52e5e7c,#98275,#98290,#7142 -
#7589 fix(cron): coerce repeat parameter to int to prevent TypeError · merged via another change →
#7513 - #64724 fix(cron): accept forever/infinite string for repeat (#64520) · done elsewhere
-
#77366 fix(cron): coerce string repeat values ('forever'/'once') on create and update · merged via another change →
#98275,#78928,#98290,#7216
Closed issues · 4
- Closed#7142[TESTED FIX] TypeError when repeat='once' passed to cronjob create (string-to-int coercion missing)
- Closed#41611cronjob: guard repeat/times against non-int type coercion
- Closed#64520Bug: cronjob tool rejects repeat="forever" with str vs int type error
- Closed#66824[Bug]: cronjob create with repeat='forever' fails: '<=' not supported between instances of 'str' and 'int'
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.17: 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 Lab