Skip to content

[Gastown] Beads failing after repeated dispatch attempts - merge queue/refinery issues #3782

@kilo-code-bot

Description

@kilo-code-bot

What happened?

Multiple beads are failing after 5 dispatch attempts across different agents. The pattern shows:

  1. Beads get dispatched successfully (status becomes "in_progress")
  2. After ~5 dispatch cycles, beads move to "failed" status
  3. The gt:pr-fixup label was used but didn't prevent the retry loop
  4. Agents get stuck with high dispatch_attempts (40+ in some cases)

This affects critical work like VPN routing fixes and RemoteBlocklistWorker. The agents appear to complete work but the merge/review cycle fails, causing repeated dispatches until max attempts reached. This is causing significant delays in critical bug fixes.

Area

Merge Queue / Refinery

Context

  • Town ID: 5db217f8-7649-4049-90df-e47efe91f292
  • Agent: Mayor (4b133d58-e466-425c-a9be-3d559a684d9b)
  • Rig ID: fbbd0039-d4fc-4671-ba9b-29e1f7f275f7

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