Cron non-streaming calls lack stale watchdog timeout
Cluster 80759. Data as of
Nothing open on GitHub. Fix merged in #80944 on 7 Aug 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 #80944. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #80944. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the cron direct API call path has no TTFB or stale watchdog, allowing cron runs to hang indefinitely on stalled non-streaming responses. The members cover the issue report and related fix attempts.
Open issues0
Open PRs0
Fixes on record
-
#80944 fix(cron): bound the inline non-streaming call with a stale watchdog (salvage of #80809)
files:
agent/chat_completion_helpers.py,tests/cron/test_cron_direct_api_call_watchdog.py,website/docs/user-guide/configuration.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#80809 fix(cron): bound the inline non-streaming call with a stale watchdog · merged via another change →
cb066a9,d7fb503,#80944,#75301
Closed issues · 1
- Closed#80759cron direct_api_call path has no TTFB/stale watchdog; cron runs hang indefinitely on a stalled non-streaming response; 600s inactivity monitor observed not firing
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
- #80944
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Aug 2026