Cairn
NousResearch/hermes-agent

Reduce false 'stuck' alerts in kanban dispatcher

Cluster 46800 · cron. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These issues and pull requests address scenarios where the kanban dispatcher incorrectly fires 'stuck' alerts, specifically when capacity deferrals, idle dispatch ticks, or a full concurrency cap are misclassified as problematic states rather than healthy or expected ones.

Open issues1

  • Issue#46800fix: _kanban_dispatcher_watcher fires false "stuck" alert when hook fills concurrency cap

Open PRs2

  • PR#46892fix(gateway): avoid false kanban stuck alerts at concurrency cap
  • PR#104144fix(kanban): classify idle dispatch ticks so a full board is not stuck

1 PR closed without merging

From the close comments: other 1

  • #94495 fix(kanban): classify capacity deferrals as healthy · other
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.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

Subsystem
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/46800.json
cluster/46800.md