Gateway cron job deadlock fixes and patches

NousResearch/hermes-agent · cluster 62151

Data as of

Nothing open on GitHub. Fix merged in #62315. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #62315. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #62315. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug report and several follow-up fixes addressing deadlocks that occur when gateway-executed cron jobs make LLM API calls, including inline execution, watchdog timeouts, and worker nesting issues.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #62315 fix(cron): keep gateway cron API calls out of nested workers

    merged to main

    files: agent/chat_completion_helpers.py, run_agent.py, tests/agent/test_cron_inline_api_call_62151.py, tests/cron/test_cron_direct_api_call_62151.py

  • #80944 fix(cron): bound the inline non-streaming call with a stale watchdog (salvage of #80809)

    merged to main

    files: agent/chat_completion_helpers.py, tests/cron/test_cron_direct_api_call_watchdog.py, website/docs/user-guide/configuration.md

3 PRs closed without merging

From the close comments: merged via another change 2 · other 1

  • #62190 fix(agent): run cron LLM calls inline to avoid gateway deadlock (#62151) · merged via another change → #62315
  • #62198 fix(cron): stop inactivity watchdogs from being blind to a wedged API call (#62151) · other → #62151, #62315
  • #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#62151[Bug] Gateway-executed cron jobs deadlock before HTTP on the 2nd+ API call — same job succeeds via CLI cron tick; chat sessions unaffected (v0.18.0)
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Merged PRs
#62315, #80944
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
7 Aug 2026

For your agent

The same facts, typed.