Cron job inactivity timer affected by host sleep
Cluster 131523. Data as of
Nothing open on GitHub. Fix merged in #131682 on 2 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131682. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131682. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where time spent with the host asleep is incorrectly counted toward cron job inactivity, causing jobs to be killed prematurely. Two are fix attempts and one is the corresponding bug report.
Open issues0
Open PRs0
Fixes on record
-
#131682 fix(cron): stop counting host sleep as job inactivity
files:
agent/session_activity.py,agent/turn_liveness.py,contributors/emails/[redacted:email],cron/scheduler.py,tests/agent/test_turn_liveness_watchdog.py,tests/cron/test_cron_inactivity_timeout.py,website/docs/developer-guide/cron-internals.md
1 PR closed without merging
From the close comments: done elsewhere 1
- #131524 fix(cron): stop counting host sleep as job inactivity · done elsewhere
Closed issues · 1
- Closed#131523Cron jobs are killed for inactivity after the host sleeps: sleep time counts as idle time
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
1.00: 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
- #131682
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Oct 2026