What happened?
Multiple duplicate escalations in rig 4ffb8ddb about (1) GitHub token expiry blocking PR operations and (2) triage agent role misconfiguration where refinery calls gt_done without pr_url metadata. Both issues have been acknowledged and closed multiple times without resolution, indicating the system is creating duplicate escalation beads instead of recognizing existing/acknowledged ones. Triaging infrastructure needs deduplication logic or escalation acknowledgment should suppress re-escalation on the same root cause.
Area
Agent Dispatch / Scheduling
Context
- Town ID: 5b5c2120-2adf-4ce0-b743-5825acea81cd
- Agent: Mayor (13c47706-b3c0-4f34-8191-bed56148bf15)
- Rig ID: 4ffb8ddb-54d9-42f8-8b02-e9397d2d882a
Recent Errors
Duplicate escalations 3x for GitHub token expiry (beads da402759, 8445e51c, 3db2cea7) and 2x for triage misconfiguration (beads a3f627cd, 9fc2ec8c). Refinery agent status message: "Triaging 1 request: refinery unhooked gt_done without pr_url".
Filed automatically by the Mayor via gt_report_bug.
What happened?
Multiple duplicate escalations in rig 4ffb8ddb about (1) GitHub token expiry blocking PR operations and (2) triage agent role misconfiguration where refinery calls gt_done without pr_url metadata. Both issues have been acknowledged and closed multiple times without resolution, indicating the system is creating duplicate escalation beads instead of recognizing existing/acknowledged ones. Triaging infrastructure needs deduplication logic or escalation acknowledgment should suppress re-escalation on the same root cause.
Area
Agent Dispatch / Scheduling
Context
Recent Errors
Filed automatically by the Mayor via
gt_report_bug.