Cronjob run action blocking and watchdog timeout
Cluster 76502. Data as of
Nothing open on GitHub. Fix merged in #76675 on 2 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 #76675. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #76675. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where cronjob action='run' blocks the calling turn synchronously, causing the inactivity watchdog to kill the parent agent, along with related fix attempts involving heartbeating or non-blocking execution.
Open issues0
Open PRs0
Fixes on record
-
#76675 fix(cron): heartbeat during cronjob(action=run) so the watchdog doesn't kill the parent turn (#76502)
files:
tests/tools/test_cronjob_run_immediate.py,tools/cronjob_tools.py,tools/environments/base.py
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
Closed issues · 1
- Closed#76502[Bug]: cronjob action='run' blocks the calling turn synchronously — inactivity watchdog kills the parent agent at 1800s
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
- Merged PRs
- #76675
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 2 Aug 2026