Skip to content

[Gastown] Dispatch system stalled - all agents idle despite open beads in active convoys #2004

@kilo-code-bot

Description

@kilo-code-bot

What happened?

Issue: All 20 polecat agents in rig b844b795 are stuck idle with current_hook_bead_id: null despite 31 open beads across 4 active convoys (Sprint 5, 6, 7, 7 Copilot).

Convoys affected:

  • ff4b8b2d (Sprint 5): 9/9 beads open
  • ad4775ec (Sprint 6): 9/9 beads open
  • bb5c6fa5 (Sprint 7): 10/10 beads open
  • db6a3100 (Sprint 7 Copilot): 1/2 beads open (implementation bead stuck)

Troubleshooting attempted:

  1. Sent nudges to 3 agents (Toast, Maple, Clover) - no effect
  2. Reset 2 agents (Toast, Maple) to idle - no effect
  3. All agents show dispatch_attempts ranging from 2-147 but none have picked up work

Expected behavior: Agents should automatically dispatch to open beads based on dependency readiness. Beads with no dependencies or satisfied dependencies should be picked up immediately.

Impact: All Sprint 5, 6, 7 work is completely blocked. No progress possible until dispatch resumes.

Town ID: 292189ed-d1e2-4cdf-b8ca-099711108660
Rig ID: b844b795-890e-4376-a81d-0b36ca312085

Area

Agent Dispatch / Scheduling

Context

  • Town ID: 292189ed-d1e2-4cdf-b8ca-099711108660
  • Agent: Mayor (b1852670-4632-4f4b-b2b5-811ce76bbfe4)
  • Rig ID: b844b795-890e-4376-a81d-0b36ca312085

Filed automatically by the Mayor via gt_report_bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions