You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trigger:issues (opened, reopened) for titles matching [aw] * failed, plus optional daily schedule sweep for missed events. Purpose: Automatically deduplicate recurring internal workflow-failure issues and convert them into a single actionable remediation thread per error signature (instead of repeated one-off failure tickets that require manual assignment). Proposed safe outputs:add-comment (link duplicate to canonical tracker), create-issue (canonical recurring-failure tracker), noop (no recurring pattern). Evidence:
Existing generic workflows do not perform this handoff/dedup orchestration:
issue-fixer (issues: opened) triages/fixes one issue at a time (gh-agent-workflows/issue-fixer/README.md)
pr-actions-fixer is manual workflow_dispatch with run ID (gh-agent-workflows/pr-actions-fixer/README.md)
duplicate-issue-detector comments on similarity but does not maintain canonical recurring failure trackers by normalized runtime signature (gh-agent-workflows/duplicate-issue-detector/README.md)
Why not covered already:
Current workflows either fix a single issue/PR or detect duplicates on open; none automatically cluster recurring [aw] operational failures into one persistent remediation issue and route future failures to it.
Open PR search reviewed for in-flight equivalent workflow additions: repo:elastic/ai-github-actions is:pr is:open ("issue-fixer" OR "pr-actions-fixer" OR "duplicate-issue-detector" OR "agentic-workflows").
Agent Suggestions
Date: 2026-06-08
1. AW Failure Handoff Coordinator
Trigger:
issues(opened,reopened) for titles matching[aw] * failed, plus optional dailyschedulesweep for missed events.Purpose: Automatically deduplicate recurring internal workflow-failure issues and convert them into a single actionable remediation thread per error signature (instead of repeated one-off failure tickets that require manual assignment).
Proposed safe outputs:
add-comment(link duplicate to canonical tracker),create-issue(canonical recurring-failure tracker),noop(no recurring pattern).Evidence:
[aw] ... failedissues with identical manual next step text: [aw] Code Duplication Detector failed #1213, [aw] Code Complexity Detector failed #1214, [aw] Bug Hunter failed #1205, [aw] Product Manager Impersonator failed #1204, [aw] Internal: Downstream Health failed #1203, [aw] Project Summary failed #1202, [aw] Internal: Agent Deep Dive failed #1224safeoutputs/outputs.jsonlmissing, auth/quota startup failures): [agent-efficiency] Recurring agent runs omit safe outputs, causing detector workflow failures #1209, [agent-efficiency] Recurring agent run failures from uv setup and copilot auth/quota handling (last 7 days) #1231issue-fixer(issues: opened) triages/fixes one issue at a time (gh-agent-workflows/issue-fixer/README.md)pr-actions-fixeris manualworkflow_dispatchwith run ID (gh-agent-workflows/pr-actions-fixer/README.md)duplicate-issue-detectorcomments on similarity but does not maintain canonical recurring failure trackers by normalized runtime signature (gh-agent-workflows/duplicate-issue-detector/README.md)Why not covered already:
Current workflows either fix a single issue/PR or detect duplicates on open; none automatically cluster recurring
[aw]operational failures into one persistent remediation issue and route future failures to it.Duplicate Checks
agent-suggestionsissue reviewed: [agent-suggestions] Auto-escalate recurring downstream-health failures into deduplicated action issues #1198 (downstream-health escalation) — related domain but distinct scope.repo:elastic/ai-github-actions is:pr is:open ("issue-fixer" OR "pr-actions-fixer" OR "duplicate-issue-detector" OR "agentic-workflows").Downstream Signals
internal-downstream-healthreports recurring downstream engine/auth failures that would also benefit from the same handoff model once applied in downstream repos: [downstream-health] Downstream health report for 2026-06-06 #1233.elastic/ai-github-actions-playground/issues/2988,elastic/ai-github-actions-playground/issues/2933).Suggested Next Steps
[aw]issues.aw-failure-handoff-coordinatoras a workflow that upserts one canonical tracker per signature.[aw]failure issues to existing canonical trackers instead of spawning parallel remediation threads.Note
🔒 Integrity filter blocked 114 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Trigger Agent Suggestions
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.