You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Town 0f3ae5da-db5f-49a8-b508-7ab409975608, rig 933bc849-eff1-4574-9955-34be2b5e22f6 (fila-palette). Convoy a68a9577-99aa-4df9-b1ee-477170154d2a ("Fix all open GitHub issues #308-#323") has 3 beads stuck in_review (#309, #312, #313) for ~3 hours. All agents are idle.
Repro steps:
Convoy had 3 beads move to in_review status around 01:17-01:34.
The refinery agent (39c3ed8e-5020-419c-9ef0-093739e3f1fd) went idle at 01:19 and never picked up the queued reviews — it had no current_hook_bead_id.
gt_agent_reset was called on the refinery — it reset to idle but still no hook, still no dispatch.
gt_bead_reassign of bead [Gastown] PR 6: tRPC Routes — Town & Rig Management #309 (9f18fe16-71c0-4edb-ad10-93c739d7ce36) to the refinery succeeded — current_hook_bead_id is now set to the bead. But the agent remains status=idle, dispatch_attempts=0.
gt_nudge in both wait-idle and immediate modes queued successfully but the agent never transitioned to in_progress or began dispatching.
Expected: Once an agent is hooked to a ready bead, the dispatch alarm should fire and the agent should transition to in_progress.
Actual: The refinery is hooked (current_hook_bead_id set) but the dispatch never fires — dispatch_attempts stays 0, status stays idle. Nudges, reset, and reassign all fail to start it.
This blocks the entire convoy: downstream beads #318, #319, #323, #314 are all dependency-blocked on these in_review beads and cannot dispatch until they close.
Tried: gt_agent_reset, gt_bead_reassign, gt_nudge (immediate + wait-idle). None caused the agent to dispatch.
Area
Agent Dispatch / Scheduling
Context
Town ID: 0f3ae5da-db5f-49a8-b508-7ab409975608
Agent: Mayor (b8ec47d7-06ee-4a9a-952a-ad5e0653574d)
Rig ID: 933bc849-eff1-4574-9955-34be2b5e22f6
Recent Errors
gt_bead_reassign for 2nd/3rd bead returned HTTP 500 "Internal server error" (refinery already hooked to one bead). gt_agent_reset and gt_nudge returned success but did not cause dispatch.
Filed automatically by the Mayor via gt_report_bug.
What happened?
Town 0f3ae5da-db5f-49a8-b508-7ab409975608, rig 933bc849-eff1-4574-9955-34be2b5e22f6 (fila-palette). Convoy a68a9577-99aa-4df9-b1ee-477170154d2a ("Fix all open GitHub issues #308-#323") has 3 beads stuck in_review (#309, #312, #313) for ~3 hours. All agents are idle.
Repro steps:
Expected: Once an agent is hooked to a ready bead, the dispatch alarm should fire and the agent should transition to in_progress.
Actual: The refinery is hooked (current_hook_bead_id set) but the dispatch never fires — dispatch_attempts stays 0, status stays idle. Nudges, reset, and reassign all fail to start it.
This blocks the entire convoy: downstream beads #318, #319, #323, #314 are all dependency-blocked on these in_review beads and cannot dispatch until they close.
Tried: gt_agent_reset, gt_bead_reassign, gt_nudge (immediate + wait-idle). None caused the agent to dispatch.
Area
Agent Dispatch / Scheduling
Context
Recent Errors
Filed automatically by the Mayor via
gt_report_bug.