[dedup-detect] Failure detection workflows re-file issues for already-tracked problems

[github-actions]

Problem

Multiple failure-detection workflows are creating new issues for failures that are already tracked by open issues, generating duplicate noise and forcing a manual "Do Not Re-File" policy as a workaround.

Evidence (Jun 18, 2026)

Workflow	New Issue	Existing Issue(s)	Status
Daily News	#40023 (Jun 18)	#39758 (Jun 17)	Duplicate, same failure
Code Simplifier	#39968 (Jun 18)	#39199, #39489, #39729	4th re-file, Day 12
Smoke Codex	#39989 + #39971 (same day)	#39986-#39994 batch	Same regression
Smoke cluster	#40042-#40047 (2nd batch Jun 18)	#39986-#39994 (morning)	Same smoke regression

Root Cause

Failure-detection workflows (e.g., [aw-failures] Failure Investigator, individual smoke tests) do not check for existing open issues with the same workflow name / error type before filing a new one.

Impact

• Issue tracker noise: ~30-40% of today's failure issues are duplicates
• Manual "Do Not Re-File" list maintained across meta-orchestrators is a workaround, not a fix
• Time wasted triaging duplicate issues
• Masking real trends (can't tell if something got worse if it's re-filed each day)

Recommendation

1. Failure Investigator workflow: Before create_issue, search for open issues with same [aw] workflow name tag and skip if found within last 7 days.
2. Smoke test workflows: Dedup by engine name — check for open Smoke issues for the same engine before filing.
3. Per-workflow tracking: Adopt a pattern where each long-running failure has exactly 1 open tracking issue, updated with comments for each recurrence.
4. Metric: Track "duplicate issue rate" — target <5%.

Affected Workflows

• [aw-failures] Failure Investigator
• Individual smoke test workflows (Copilot, AOAI, Codex, Claude, Gemini, Pi, Antigravity)
• Any workflow using auto-create_issue on failure without dedup check

Generated by ⚡ Agent Performance Analyzer - Meta-Orchestrator · ◷

• expires on Jun 20, 2026, 5:57 AM UTC-08:00

[copilot-swe-agent]

The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 1140:29479D:57DD5E4:14616073:6A340C68)

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-06-20T13:57:08.265Z.

Closed by Workflow