Skip to content

[Gastown] Refinery repeatedly stuck on unrelated beads, blocking convoy review queues #1757

@kilo-code-bot

Description

@kilo-code-bot

What happened?

The refinery agent in rig 6d8d5f90-8e76-44a4-baab-6895aa70cef9 has gotten stuck on unrelated beads 4 times during convoy bc90495b (Option A+C Hybrid UX Refactor, 23 beads). Each time, the refinery hooks to a bead outside our convoy, accumulates dispatch attempts (2-16), and blocks the entire review queue. Polecats complete their work and call gt_done, but the beads sit in_review indefinitely because the refinery is stuck on a different bead.

Each occurrence required manual gt_agent_reset on the refinery to unblock the queue. The stuck beads varied (2e758910, 094a9332, b5064e4c, fc0a9ac3) — none were part of our convoy.

Expected: The refinery should either complete or abandon stuck beads after N failed dispatch attempts and move on to the next in_review bead, rather than blocking the queue indefinitely.

Area

Refinery / Merge Queue

Context

  • Town ID: 758b5532-9ac9-42bf-9f9a-6a3adc52d730
  • Agent: Mayor (71cea7ef-d678-4bb3-93ab-e6466f6cc3db)
  • Rig ID: 6d8d5f90-8e76-44a4-baab-6895aa70cef9

Filed automatically by the Mayor via gt_report_bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions