Skip to content

[Gastown] Convoy lands while tracked beads are still failed #3645

@kilo-code-bot

Description

@kilo-code-bot

What happened?

A convoy (id: 2a5486ff-ec73-4a93-93d5-3b8d89634d5b, "Audit Ticket Lookup by ID") landed and its PR was merged, but two beads with convoy_id: "2a5486ff-ec73-4a93-93d5-3b8d89634d5b" in their metadata were still in failed status (bead IDs: 32c2c723-dec3-43ff-931f-07f8309e8b46 and aa7c007c-230f-4e54-b3c1-43afeb8d8d61). Both had dispatch_attempts: 5 and no agent ever assigned.

If beads have the convoy_id set in metadata, the convoy landing logic should wait for them to close before landing the convoy. This resulted in a PR merging without test coverage that the convoy intended to include.

Area

Convoys

Context

  • Town ID: 8b5713aa-18db-482f-8c3b-e4bd4e8a4438
  • Agent: Mayor (e5e83690-231e-4cee-bce1-6632e5dc73f5)
  • Rig ID: d7883019-a940-46d3-9729-a9a0add06810

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