Nothing open on GitHub. Fix merged in #124035 on 26 Sep 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #124035. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #124035. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where error or failure notifications for recurring cron jobs are suppressed on the final run, even when no further retry is possible. The work focuses on ensuring unreachable or failure signals are surfaced rather than held back indefinitely.
Open issues0
Open PRs0
Fixes on record
-
#124035 fix(cron): stop holding failure notices for retries that can never run (salvage #123141)
files:
cron/unreachable_retry.py,tests/cron/test_unreachable_retry.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#109991 fix(cron): deliver unreachable errors on the final recurring run · done elsewhere →
cb399b5,#124035
Closed issues · 1
- Closed#109990Final repeat-limited cron failure is silenced even though no retry can run
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.67: 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
- Merged PRs
- #124035
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 26 Sep 2026