hermes - 💡(How to fix) Fix [Bug]: Kanban auto-unblock is too eager [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#28903Fetched 2026-05-20 04:01:12
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fix / Workaround

Currently blocked Kanban tasks get auto-unblocked back to Ready if they don't have a running parent dependency (PR #28377). However, this doesn't just trigger when a dependency is completed - rather it merely checks that there are no running/pending dependencies at dispatch time. Thus, whenever dispatcher runs, it always moves any Blocked task without current dependencies back to Ready, including:

  • Tasks that never had a dependency
  • Tasks whose dependencies were already completed before the blocking run
  • Even tasks that were just created with --initial-status blocked if they don't have links yet
  • Potentially tasks that were put to Blocked but dispatcher ran before dependencies were created, etc.
hermes kanban create --initial-status blocked --json 'TEST' --body 'this is a test'
hermes kanban dispatch
hermes kanban show t_xxxxx // ready !!
hermes kanban create --json 'TEST' --body 'block yourself'
hermes kanban assign t_xxxxx default
hermes kanban dispatch
// wait
hermes kanban show t_xxxxx // blocked
hermes kanban dispatch
hermes kanban show t_xxxxx // running !!

Code Example

hermes kanban create --initial-status blocked --json 'TEST' --body 'this is a test'
hermes kanban dispatch
hermes kanban show t_xxxxx // ready !!

---

hermes kanban create --json 'TEST' --body 'block yourself'
hermes kanban assign t_xxxxx default
hermes kanban dispatch
// wait
hermes kanban show t_xxxxx // blocked
hermes kanban dispatch
hermes kanban show t_xxxxx // running !!

---

Report       https://paste.rs/SrxB5
agent.log    https://paste.rs/Y6HC6
gateway.log  https://paste.rs/M97R2

---
RAW_BUFFERClick to expand / collapse

Bug Description

Currently blocked Kanban tasks get auto-unblocked back to Ready if they don't have a running parent dependency (PR #28377). However, this doesn't just trigger when a dependency is completed - rather it merely checks that there are no running/pending dependencies at dispatch time. Thus, whenever dispatcher runs, it always moves any Blocked task without current dependencies back to Ready, including:

  • Tasks that never had a dependency
  • Tasks whose dependencies were already completed before the blocking run
  • Even tasks that were just created with --initial-status blocked if they don't have links yet
  • Potentially tasks that were put to Blocked but dispatcher ran before dependencies were created, etc.

This is notably harmful for any workflow that uses Blocked for "waiting for external unlock" (e.g. human review or approval).

Steps to Reproduce

Easiest demo:

hermes kanban create --initial-status blocked --json 'TEST' --body 'this is a test'
hermes kanban dispatch
hermes kanban show t_xxxxx // ready !!

Or the fancy way:

hermes kanban create --json 'TEST' --body 'block yourself'
hermes kanban assign t_xxxxx default
hermes kanban dispatch
// wait
hermes kanban show t_xxxxx // blocked
hermes kanban dispatch
hermes kanban show t_xxxxx // running !!

Expected Behavior

Task is blocked

Actual Behavior

Task is ready / running

Affected Component

Other

Messaging Platform (if gateway-related)

No response

Debug Report

Report       https://paste.rs/SrxB5
agent.log    https://paste.rs/Y6HC6
gateway.log  https://paste.rs/M97R2

Operating System

Ubuntu 24.04

Python Version

No response

Hermes Version

No response

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

PR #28377

Proposed Fix (optional)

Fix depends on the intended vision/semantics of "Blocked" column, as it seems to have moved away from meaning "unfinished stuff that won't move until some human touches it" - if so maybe such column needs to be added?

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Bug]: Kanban auto-unblock is too eager [1 comments, 2 participants]