Nothing open on GitHub. Fix merged in #131071 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 #131071. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131071. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a problem where the gateway's restart wait incorrectly holds for cron runs that are already within a restart-safe scope, potentially blocking turns for up to 30 minutes. The fix skips such scoped cron runs from the restart wait, keyed per profile.
Open issues0
Open PRs0
Fixes on record
-
#131071 fix(gateway): skip restart-safe scoped cron runs in the restart wait, keyed per profile
files:
cli-config.yaml.example,contributors/emails/[email protected],cron/scheduler.py,gateway/run_shutdown.py,tests/cron/test_restart_safe_worker.py,tests/gateway/test_restart_drain.py,website/docs/getting-started/updating.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#130988 fix(gateway): restart wait must not hold for cron runs in their own restart-safe scope · superseded by another PR →
#131071
Closed issues · 1
- Closed#130987gateway: restart wait holds for cron runs that already outlive the restart (up to 30 min of refused turns)
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
- #131071
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Oct 2026