Repository navigation
[Gastown] Agent dispatch not triggering after reset - Toast stuck idle despite bead assignment #1574
Closed as not planned
Description
What happened?
After resetting Toast to idle and reassigning to bead 18ee7d34-2eaf-4f6a-85d9-dee0beb8db59, the agent remains idle and doesn't start work. The dispatch alarm doesn't appear to be triggering. This is blocking PR #12 comments from being addressed.
Repro steps:
- Toast was stuck with 0 dispatch attempts on in_progress bead
- Reset agent to idle with gt_agent_reset
- Reassigned bead to Toast with gt_bead_reassign
- Toast remains idle, no dispatch triggered
Expected: Agent should start working on assigned bead
Actual: Agent stuck idle, bead in_progress but no agent activity
Area
Agent Dispatch / Scheduling
Context
- Town ID: 4c26ec56-cf58-4f79-85b7-a7d15409fcb4
- Agent: Mayor (bdf4704e-bf89-4c2c-a6aa-81c51b2e127b)
- Rig ID: bb97411b-1d96-46ba-94d4-d2626d279b4a
Filed automatically by the Mayor via gt_report_bug.
Activity
jrf0110 commentedon Mar 30, 2026
Closing as duplicate of #1701
Both issues describe the same bug: agent is idle with a bead hooked but the reconciler does not dispatch it. #1701 is the more recent report with the same symptoms. The root cause is the same — reconciler Rule 2 (dispatch idle+hooked agents) either has a guard condition that prevents firing, or the dispatch side effect fails silently.
See also #1487 (same class of bug — agents stuck, dispatch not triggering) and #1653 (dispatch circuit breaker).