What happened?
The triage resolve API is consistently returning 500 errors in rig 1c8bcfd9 (Aruna). This has caused dozens of triage batch beads to fail (tagged gt:triage), all with the same body "Process all pending triage request beads and resolve each one." The failures started around 2026-05-22T00:39 UTC and continued every ~90 seconds through at least 2026-05-22T02:30 UTC. The triage agent (4004c25b) correctly escalated one item to the Mayor, but the resolve call itself fails with a 500, causing an infinite retry loop. This is blocking triage resolution for any work in this rig.
Area
Bead Board / Dashboard
Context
- Town ID: 82cb9958-d7d8-45e5-a019-8e578c4c7782
- Agent: Mayor (f63b13ee-3264-4a63-baac-e5c231e11209)
- Rig ID: 1c8bcfd9-ceb0-4148-952e-1955525c4f3d
Recent Errors
gt:triage beads failing with triage resolve API 500 errors in rig 1c8bcfd9-ceb0-4148-952e-1955525c4f3d. Over 60 failed triage batch beads created since ~2026-05-22T00:39 UTC.
Filed automatically by the Mayor via gt_report_bug.
What happened?
The triage resolve API is consistently returning 500 errors in rig 1c8bcfd9 (Aruna). This has caused dozens of triage batch beads to fail (tagged gt:triage), all with the same body "Process all pending triage request beads and resolve each one." The failures started around 2026-05-22T00:39 UTC and continued every ~90 seconds through at least 2026-05-22T02:30 UTC. The triage agent (4004c25b) correctly escalated one item to the Mayor, but the resolve call itself fails with a 500, causing an infinite retry loop. This is blocking triage resolution for any work in this rig.
Area
Bead Board / Dashboard
Context
Recent Errors
Filed automatically by the Mayor via
gt_report_bug.